Automation

    Connect once. Then stop pulling reports.

    Every number in Unilytic comes from Amazon, and the least interesting part of running an FBA business is fetching it. Authorise once through Login with Amazon and the data arrives on its own, every morning before your working day — the ledger, your inbound shipments, returns, reimbursements and order prices.

    Eight data setsRuns before 07:30 ISTYou pick what syncsTells you when it breaks
    One authorisation

    You never hand over a password.

    Connecting runs through Amazon's own Login with Amazon screen, so your Seller Central credentials are entered on Amazon's site and never reach Unilytic. What comes back is a token, which is stored encrypted, and which you can revoke from Amazon or from Unilytic whenever you like. Unilytic only reads — it never creates a listing, edits a price, or touches an order. On the first connection it pulls roughly ninety days of ledger history so your analytics are useful immediately rather than after a month of waiting.

    • Authorised on Amazon's screen — no Seller Central password is ever shared.
    • Read-only. Unilytic reads your data; it never writes to your account.
    • Backfilled on day one, so the first send list is based on real history.
    Runs before you do

    A sync you never have to remember.

    Each organisation is assigned its own slot between 06:00 and 07:30 IST — spread deterministically so a growing customer base never hits Amazon in one burst, and timed for after Amazon's previous-day ledger has settled but before your day starts. Returns and reimbursements are re-fetched across a fourteen-day window, because Amazon backdates them. If a part fails it is retried, and if the whole thing has been failing for days you get told rather than left to notice a stale dashboard on your own.

    • A per-organisation slot in the 06:00–07:30 IST window, so nothing stampedes.
    • A fourteen-day recon window that absorbs Amazon backdating a return.
    • Retries, then an email — you hear about a stalled sync instead of discovering it.
    • A Stop button while it runs, so a sync you started by mistake is not something you wait out.
    • Nightly runs on Pro and Business. Connecting Amazon, the first import and manual syncs are on every plan.
    Control

    Automatic, but not opaque.

    Automation you cannot see into is just a black box on a timer. Every part of the sync is visible, and most of it is yours to switch.

    Sync on demand, and stop it

    Waiting until tomorrow is not always an option, so you can run a sync yourself — and stop one mid-run if you started it by mistake. Press it twice and the second press joins the run already going rather than starting a second fetch.

    A catalogue that fills itself

    Unilytic builds a master catalogue mapping SKU to FNSKU to ASIN, with descriptions and categories, from your listings report. That mapping is what lets a warehouse barcode scan resolve to a product.

    Why this matters

    Data you have to fetch by hand is data that goes stale.

    Manual reporting fails in a specific and predictable way. It works fine in month one, slips to weekly by month three, and by the time it actually matters — the week before a sale event, or the month you are chasing reimbursements — the last export is nineteen days old and nobody wants to admit it. The decisions do not stop being made; they just get made on stale numbers. Automating the fetch is not about saving the ten minutes. It is about the numbers being right on the day you were not paying attention.

    Eight data sets, every morning
    The ledger, shipments, returns, reimbursements and order prices arrive before your working day.
    Breakage is loud
    A stalled sync or an expired authorisation sends an email instead of failing quietly.
    No password ever changes hands
    Authorisation happens on Amazon's screen, and the resulting token is stored encrypted and revocable.

    Common seller mistakes

    • Planning replenishment from a stale exportA ledger downloaded eleven days ago describes a business that no longer exists. Every quantity computed from it inherits the error.
    • Only pulling returns data when chasing a claimReimbursement windows expire. By the time a quarterly review surfaces a discrepancy, some of it is no longer claimable at all.
    • Assuming silence means everything is fineA dashboard with stale data looks identical to a dashboard with fresh data. Without an alert, a broken integration can go unnoticed for weeks.
    • Letting one person own the exportWhen the reporting routine lives with a single team member, it stops the week they are on leave — and nobody else knows it stopped.
    Reference

    What Unilytic syncs from Amazon.

    Eight data sets, each fetched and tracked independently so one slow report never blocks the rest. Every plan can connect Amazon, run the first import and sync manually; the unattended nightly schedule is a Pro and Business feature.

    Scroll the table sideways for the remaining columns.

    Amazon SP-API data sets Unilytic imports, and which run on the nightly schedule (Pro and Business).
    Data setWhat it powersNightly by default
    Inventory ledgerPer-warehouse stock, cover and the send listYes
    Inbound shipmentsIn-flight units and Future StockYes
    Customer & seller returnsReturns reconciliation and warehouse scan auto-fillYes
    ReimbursementsWhat Amazon has already paid backYes
    Order pricesThe revenue side of ₹/day at riskYes
    Product catalogSKU ↔ FNSKU ↔ ASIN mapping for scanningOn request
    Listing pricesValue estimates for claimsOn request
    Refunds & SAFE-T claimsRefund reconciliation and SAFE-T lookupsWhere available
    Questions

    Amazon sync, answered.

    How do I connect Unilytic to my Amazon seller account?01

    Through Login with Amazon, the standard SP-API authorisation flow. You approve access on Amazon's own screen, so your Seller Central password is never entered into Unilytic. The resulting token is stored encrypted, and you can revoke it at any time from Amazon or from within Unilytic.

    What data does Unilytic pull from Amazon?02

    Up to eight data sets: the inventory ledger, inbound shipments, your product catalogue, customer and seller returns, reimbursements, listing prices, order prices, and refunds including SAFE-T claims. Five of them run nightly by default and the rest are available on request, with refunds depending on the permissions the integration currently carries.

    When does the automatic sync run?03

    Each organisation gets its own slot between 06:00 and 07:30 IST. The slot is derived from your organisation identifier, so it is stable across restarts and spreads load rather than every account hitting Amazon at once. That timing puts it after Amazon's previous-day ledger has settled and before your working day begins.

    Is the automatic nightly sync included on the free plan?04

    The unattended nightly schedule runs on Pro and Business. Every plan, including Free, can connect Amazon, run the full first import, and sync manually whenever you want — so you can evaluate the whole integration before paying for it. What Pro and Business add is not having to remember.

    Can I still upload a CSV instead?05

    Yes. Uploading the Inventory Ledger by hand remains fully supported — it is the fastest way to try Unilytic before authorising anything, and it stays available afterwards.

    What happens if the sync fails?06

    Failed parts are retried during the day with a gap between attempts. If your organisation goes several days without a successful sync, or Amazon stops accepting the stored authorisation, Unilytic emails you. Those alerts are always on and are never blocked by your plan's email quota, because a silent integration failure is the one thing you cannot afford to miss.

    Can I trigger a sync myself?07

    Yes, and you can stop one mid-run too. There are sensible guard rails, because Amazon's report quota is shared across your whole seller account and refills slowly: pressing sync again while one is running joins the run in progress rather than starting a second fetch, a completed full sync waits a few minutes before another can start, and reports Amazon only regenerates once a day refuse a same-day repeat because the second download would be byte-identical. Normal use never meets these limits — they exist so one impatient tab cannot starve your own nightly sync.

    Get started

    Connect Amazon once, then forget about it.

    No card · Built for Amazon India · Email support from the founder.