Fretron CommerceOS
Fretron CommerceOS is a multichannel order and warehouse management application. A seller authorizes their sales channels once, and every order — from a marketplace, a D2C storefront, or an offline channel — lands on one order record backed by one inventory ledger, then runs through allocation, picking, packing, dispatch, returns, and settlement reconciliation without being re-keyed into a second system.
Who it’s for
Marketplace integration
These capabilities are verified in production against a live Amazon India seller account. A seller authorizes the connection themselves; Fretron accesses only what that authorization permits.
Live · verified in production
A seller connects their marketplace account by granting Fretron CommerceOS access through the marketplace’s own consent screen. CommerceOS never asks for, and never stores, marketplace account passwords. The authorization exchange returns a refresh token which is encrypted before it is stored, and the seller can revoke the authorization from their own seller account at any time.
Live · verified in production
CommerceOS reads the seller’s live listings from the marketplace — seller SKU, marketplace product identifier, title, product type, and images — and creates a listing snapshot per channel. Each channel listing is then linked to one internal item record, so a product sold under different SKUs on different channels resolves to a single item.
Live · verified in production
Channel SKUs map to internal item masters, and channel fulfilment nodes map to internal warehouses and stock locations. That mapping is what lets an order from any channel be allocated, picked, and packed against the same inventory ledger as every other channel, rather than each channel running its own stock pool.
Live · verified in production
CommerceOS pulls orders and order line items from the marketplace and normalizes each one into an internal sales order with its lines, quantities, prices, and fulfilment node. Order pulls run on demand from the operator console and on a targeted refetch when the marketplace reports an order change. Cancellations are pulled alongside orders.
Live · verified in production
Available-to-sell quantities computed on the CommerceOS inventory ledger are published back to the marketplace listing, and the acknowledgement from the marketplace is recorded against the job. This is what keeps a single stock number honest across channels instead of each channel drifting on its own count.
Fulfilment capabilities
These are built and integrated, and are completing live verification on production seller accounts. They are listed separately so there is no ambiguity about what is proven in production today and what is still being proven.
In launch verification
Acknowledging orders back to the marketplace and confirming shipment with carrier and tracking details, so the marketplace and the buyer see the same dispatch state CommerceOS holds.
In launch verification
A pack session on the warehouse floor moves an order through created, in-progress, and completed states with channel-specific pack rules. Shipping labels, packing slips, and invoices are retrieved from the marketplace’s own document APIs and stored as document artifacts against the order — CommerceOS does not fabricate marketplace labels locally.
In launch verification
For sellers fulfilling their own shipments, CommerceOS supports the marketplace’s merchant-fulfilment, shipping, and scheduled-pickup flows: rate and slot selection, shipment creation, and retrieval of the resulting printable documents.
In launch verification
Buyer shipping addresses are restricted data. CommerceOS retrieves them only through the marketplace’s restricted-data-token flow, only for an active self-ship account with restricted access explicitly enabled, only for a shipping or packing purpose, and only for a user holding the relevant permission. The address is used to produce the label or carrier handoff and is not retained as a stored copy; an audit record of the access — who, when, which order, which purpose — is written without the address values. Live use additionally requires Amazon to approve the Direct-to-Consumer Shipping restricted role for the application.
In launch verification
Return events are pulled from the marketplace, matched to the originating order, and used to move stock back onto the inventory ledger through the returns module, so returned units become sellable again on the same record.
In launch verification
Settlement reports and finance transactions are pulled and reconciled line by line against the orders CommerceOS holds, flagging short payments, over payments, and fee, commission, or tax mismatches.
Modules
A seller enables the modules they need. Each is licensed individually — see pricing.
| Module | What it covers |
|---|---|
| Order management (OMS) | Order capture, allocation, routing across warehouses, and status through to delivery. |
| Warehouse management (WMS) | Inbound, putaway, the inventory ledger, wave and pick planning, packing, and outbound dispatch. |
| Channel integrations | Marketplace, D2C storefront, and offline channel connections against one order and inventory record. |
| Returns | Return capture, disposition, and putback of sellable stock. |
| Reconciliation | Settlement and payout reconciliation against orders, fees, commissions, and taxes. |
| GST compliance | E-invoice and e-way-bill generation through licensed Indian GST suvidha providers. |
Onboarding
Data handling
The full detail — what is collected, why, how long it is kept, who processes it, and how to request deletion — is in the Fretron CommerceOS privacy notice.
Independence
Fretron CommerceOS is developed and operated by Fretron Private Limited, an independent software provider. Fretron is not affiliated with, sponsored by, endorsed by, or certified by Amazon or any other marketplace. Marketplace names are used only to describe the channels a seller can connect. All marketplace trademarks belong to their respective owners.
FAQ
Bring your channel list, SKU count, and warehouse footprint — we will show you where your stock and order records diverge today.
How to review:
Tip: the homepage has two headline versions — review both via /?hero=a and /?hero=b.