How a Supplier Side Reseller Integration Works
Six parts, from the catalogue you publish to the monitoring you run per reseller. Small programs can start with the first two and handle orders by email.
A feed resellers can load as is Outbound feed design
The feed is built from your ERP or product system with fields chosen for resellers: SKU, GTIN, brand, title, long description, bullet features, attributes such as size, colour and material, image URLs, weights and carton dimensions, RRP, trade price, availability, lead time and a lifecycle flag for new, active, discontinued and replaced by. Availability is usually shown as a band or a capped quantity rather than your real on hand figure, so a reseller sees ‘10+’ or ‘Low’ and you do not oversell or reveal stock depth.
Right file, right reseller, right price Formats, delivery and access
The same catalogue is delivered as a scheduled CSV over SFTP, as an API endpoint, or mapped into a retailer’s own template where a large retailer insists on one. Each reseller has their own credentials, an assigned price list and an authorised range, and the feed is filtered accordingly. Stock and price usually refresh more often than content: perhaps hourly for availability and daily for full product data. Credentials can be revoked when a reseller relationship ends, which a shared link never allows.
One validated order queue Dropship order intake
API, EDI, portal and emailed purchase orders are normalised into the same order record. Each order carries the reseller account, their PO number, line references, the end customer’s name, delivery address and phone, and any delivery instructions. Validation runs before release: unknown SKUs, discontinued lines, prices that do not match the reseller’s price list, PO boxes for couriers that will not deliver to them, and duplicate PO numbers. Failures go back to the reseller with a specific reason, not a generic rejection.
Parcel looks like the retailer sent it Blind shipping and despatch
Dropship orders are picked like any other but packed differently. The packing slip is unbranded or carries the retailer’s name and logo, prices are left off, and your own invoice and marketing inserts never go in the box. The carrier label sender name and return address are set per reseller according to your agreement, and the despatch notice and tracking number are sent back to the reseller against their PO within minutes of manifest, including partial despatches when a line is backordered.
One tax invoice per order to the retailer Retailer invoicing
You sell to the retailer, so the tax invoice goes to the retailer’s ABN at their trade price, with GST shown as your accountant advises, the retailer’s PO number quoted, and freight and any dropship handling fee as separate lines. Invoices are raised on despatch, not on order, so partial shipments are invoiced only for what left. Where a retailer prefers consolidated invoicing or a statement, the same data is grouped by period. The consumer never sees your invoice.
Clear RMA path and per reseller health Returns, faults and monitoring
Returns and faulty goods follow an agreed RMA process between you and the retailer: the retailer requests an authorisation, you issue an RMA number and a return label, the goods come back to you, and a credit note is raised to the retailer. Alongside that, each reseller has a simple health view: when they last pulled the feed, how many orders failed validation, average time from order to despatch, tracking latency and returns rate, so problems are found before the reseller raises them.