Short answer: yes, but only if the item-level data is already being fed into ShipStation from the channel you�d use for freight orders.
Below is a detailed overview of what ShipStation can (and can’t) do, and some practical ways teams create a single “source of record” for shipping dates and line-item detail.
1. How ShipStation stores order & item data
- Order import – ShipStation never creates orders on its own. It imports them from connected selling channels (e-commerce site, ERP, EDI, manual CSV upload, or the ShipStation API).
- Item-level detail – If the upstream system includes SKU, name, quantity, and customs values, ShipStation will store that at the line-item level. You can see this in:
• Orders > click an order > Items tab
• Shipments > click a shipment > Items tab
• Reports > Shipment Item Detail report - Shipment record – When a label is created, ShipStation stamps the shipment with:
• ship-date/time (based on label creation or label void/reprint)
• carrier & service
• tracking number (blank for freight if you use “Other” carrier)
If your freight channel is already pushing line-item data into ShipStation, you automatically have a per-item record tied to the shipment date.
2. Special considerations for FREIGHT
| Scenario | What works | Gaps & work-arounds |
|---|
| You ship LTL via a standard API-connected freight carrier (e.g. Estes, Worldwide Express, Seko) | Connect carrier in Settings › Shipping › Carriers → create labels/PROs directly in ShipStation. | Most freight APIs return a PRO (tracking) #, but some adjunct services don’t populate weight-based rate quotes – you may need to enter dims manually. |
| You create BOLs in a TMS or directly on the carrier site | In ShipStation set Carrier = “Other” and manually key the PRO/BOL; or use ShipStation API to mark the order as shipped from the outside system. | No live rate quote inside ShipStation; you must keep service names consistent for reporting. |
3. Making ShipStation your single source of shipment dates
- Force all channels (e-comm, ERP, EDI) to mark orders unshipped until ShipStation prints the label/BOL.
- Use the ShipStation API to
• push freight BOL numbers into ShipStation, or
• pull the Shipments endpoint nightly and load to your BI/ERP if that is the master database. - Disable auto-cancel & auto-mark-as-shipped rules in upstream systems so ShipStation remains authoritative.
- Leverage Reports › Shipment Item Detail for a ready-made CSV that contains: order #, SKU, quantity, shipment date, carrier, tracking/PRO.
4. Limitations & things to watch
• No inventory decrement – ShipStation is not an inventory system; if you need real-time stock after freight shipments you’ll still need an ERP or IMS.
• No true multi-package BOL – An LTL shipment with 4 pallets shows as one shipment record; detail beyond that lives only on the BOL.
• Return freight not automated – Return BOLs must be created outside ShipStation or via custom API calls.
5. Typical architecture when freight is in play
6. Next steps
- Confirm that your channel feed (ERP, CSV, API) is sending SKU-level data into ShipStation for freight orders.
- Map freight services consistently (e.g. “LTL-Estes”) so reports are clean.
- Decide whether ShipStation’s Shipment Item Detail report or an API pull will feed your master database.
Bottom line: If your upstream system can hand ShipStation the line-items for each freight order, then ShipStation can serve as the single place to look up both the item sold and the actual ship date. If item-level data never comes into ShipStation, you’ll have to combine ShipStation’s shipment export with your order data in another system to get the full picture.
Let me know if you’d like sample API calls, a reporting workflow, or have other questions! 😊