Catalogs and order routing
The order goes where the stock is.
Keep source catalogs and stock in one place, quote an order, split it by source and read the routing record behind each line. The same account can build the EDI file and the ERP export.
- Source catalogs
- Stock and cost
- Quotes
- Order splits
- Carrier rates
- EDI and ERP files
The routing endpoint returns this record.
Inside the product
What you can do in the order desk
Catalogs
One product, many source offers.
Join source offers to a product by UPC. Keep price, stock, MAP and the drop-ship flag beside the offer. A catalog refresh updates stock and cost without creating a second product.
Offers with a known master UPC join to one product.
Quotes
A quote shows its work.
Price a basket from current source stock and cost. Every line returns the chosen source, the unit price, the shipping cost and up to five alternatives, so you can see why one source won. A quote does not reserve stock or hold a price.
A quote is advisory and does not reserve stock.
Splits
When lines land at different sources, the order splits.
In optimal mode, route each line to a source that can fill it. When lines land at different sources, the order becomes more than one fulfillment order. Each child keeps its own source, lines and routing record.
Each fulfillment order names its source.
Carrier rates
Sample rates, labelled as samples.
Compare carrier services for a parcel. The response carries the estimated weight, zone and excluded services it used, so a sample is not mistaken for a booked rate. A live carrier connection is planned, not built, so every rate in this build is an example.
No live carrier account is implied.
EDI
The files a trading partner asks for.
Build an 850 purchase order from an order and read 855 acknowledgements, 856 advance ship notices, 846 inventory and 810 invoices. Files are validated before they are accepted. A malformed envelope is rejected with a reason.
ISA*00* *00* *ZZ*ROLLSTAMP *ZZ*SUPPLIER *260218*1200*U*00401*000000001*0*P*> GS*PO*ROLLSTAMP*SUPPLIER*20260218*1200*1*X*004010 ST*850*0001 BEG*00*SA*10482**20260218 SE*4*0001 GE*1*1 IEA*1*000000001
A file for your trading partner, not a transport.
Exports
One document set per request.
Export orders, purchase-order lines, shipments or invoices as JSON or CSV, from an optional since date. The export returns that document set as JSON fields or CSV columns your ERP import can map.
One document set per request.
The boundaries
Order rules you can audit.
The reason travels with the order
A routed line stores why the source won. The routing endpoint returns the rule, reason and candidates. A later price change does not rewrite the routing record on an order. A quote is advisory and does not hold stock or price.
Stock is per source
Routing reads stock per source. It does not pool quantities into one number and guess a split. Each source reports its own quantity.
EDI is a file exchange
RollStamp builds and reads the named transaction sets. The trading partner still owns the agreement. AS2, SFTP or VAN transport is not built.
One document set per export
The ERP export returns orders, purchase-order lines, shipments or invoices. It does not combine them, and it leaves your ERP mapping to the import.
Questions, answered plainly.
Does RollStamp connect to every source?
No. Catalogs join offers from the sources you configure, and EDI handles the documented transaction sets. Marketplace adapters and ERP adapters beyond the built JSON and CSV export paths are planned.
Can I route by cost alone?
By default, an order uses the source and SKU you name (exact). In optimal mode, RollStamp picks a source that can fill the quantity, ranking by landed cost unless the account ignores shipping costs. Stock still has to cover the order. The rule and candidates are recorded with the order and returned by the routing endpoint.
Are carrier rates live?
The carrier rate path returns samples only. A live carrier account connection is planned, not built, and sample responses are labelled as samples.
Bring an order you split by hand.
We will join two source offers, route the line, and show the EDI and export paths without pretending a missing adapter exists.