Catalogs and order routing API
The catalog joins source offers with a known master UPC to one product. Stock and cost are kept per source, and routing reads them there rather than guessing from one pooled number. An order can be routed to one source or split across several.
Routing
GET /v1/orders/{id}/routing shows why each line went where it did. The record keeps the source, the rule, the reason and the candidates behind the choice, so a later price change does not rewrite an earlier decision.
Stock and cost
GET /v1/inventory/{sku} takes a UPC or a source SKU and returns stock and cost at each source that carries the product. A quote uses those values and returns the chosen source and alternatives with each line. It does not reserve stock or hold a price.
Carrier rates
POST /v1/shipping/rates returns a rate sample, and carrier_rates: true adds samples to a quote. A sample is labelled as a sample. A live carrier account connection is planned, not built.
EDI
Build an 850 purchase order with GET /v1/orders/{id}/edi. Send 855, 856, 810 and 846 inbound files to POST /v1/edi/inbound; the response includes a 997. A malformed envelope is rejected with a reason, not accepted silently.
ERP exports
GET /v1/erp/export returns flat JSON or CSV for an ERP import. Choose orders, purchase-order lines, shipments or invoices, and optionally a since date. The export returns that document set with a fixed set of fields; the ERP import owns the mapping.
Vendor portal
POST /v1/vendors creates a vendor and a portal token. The vendor signs in at the vendor portal with that token, not an API key.