The process of label generation in the NEW wholesale flow is determined by two key factors related to the order: its Type and its Origin.
Order Type: The categorization of a wholesale order dictating how labels are generated and how the items are packed:
- Courier Orders: These involve individual boxes that are shipped via a standard parcel carrier (e.g., UPS, FedEx). Labels are generated per box.
- Freight Orders: These are larger shipments that are processed and shipped together on a pallet. The labeling process is geared toward LTL (Less-Than-Truckload) freight.
Order Origin: Where the order was imported into ShipHero from.
- EDI (Electronic Data Interchange): An order imported via EDI has specific invoice and labeling parameters that must be met. These configurations are typically managed by our integrations team and via the API.
- Non-EDI: Orders classified as Non-EDI are those that are manually created within ShipHero, imported through a native store integration, or created via the API.
We have integrations with SPS & Netsuite, but also our public API was enhanced with the "EDI-agnostic" principle, meaning that it could be used to connect with any EDI. Here are some useful articles:
EDI via SPS: ShipHero & SPS Commerce Integration, Connecting to SPS Commerce, Mapping SPS orders
EDI via Netsuite: NetSuite Integration
EDI via API: ShipHero Developer Portal, Public API Schema, Webhook Documentation (includes examples for ASN and Carrier Label Generation webhooks)
-
End-to-End Wholesale Flow Example:
https://developer.shiphero.com/docs/flows/wholesale-orders-packed-outside-shiphero/ This guide describes a complete workflow where the Public API is used to handle a Wholesale order entirely outside of ShipHero's UI, from creation to fulfillment.