Skip to main content
The last mile between an approved order and your carrier’s system has traditionally meant one more manual step: taking the data you just reviewed and approved, and rebuilding it into whatever upload format your carrier expects. StackCube removes that step entirely. As soon as an order is approved, a carrier-ready CSV file is available to download. The file is formatted to match your carrier’s upload specification, which means you can go straight from approval to dispatch without touching the data again.

How carrier export works

1

Approve the order

Complete your review in the order queue — verify SKU matches, confirm pricing, and approve the order or individual lines. Approval is the trigger that makes the carrier CSV available.
2

Download the carrier CSV

From the approved order, select Download CSV. StackCube generates the file instantly using the approved order data and your configured carrier format. No additional input is required.
3

Upload to your carrier system

Take the downloaded file directly to your carrier’s upload portal or file intake process. The file is structured to match the carrier’s expected format, so no reformatting is needed before upload.

Carrier format options by plan

All plans

Standard carrier CSV download available immediately after order approval. Download individual orders as needed.

Scale

Custom carrier formats available. Configure the CSV output to match the exact column layout, field names, and encoding your carrier requires.

Enterprise

ERP and API integration for automated file delivery. Approved orders can be pushed directly to your ERP or logistics system without manual download steps.

Why this matters

Before StackCube, a typical order-to-carrier workflow looked like this: receive order via email → copy data into a spreadsheet → reformat columns to match carrier spec → upload. Every manual step introduces an opportunity for error, and rebuilding the upload file after every approval is time your team could spend on something else. With StackCube’s carrier export, the approved order data you already verified in the review queue becomes the carrier file. There is no re-entry, no reformatting, and no risk of transcription errors between approval and dispatch.
Before you process your first order through to carrier export, open your carrier format settings and confirm the output matches your carrier’s current upload specification. Carrier format requirements do change, and verifying the configuration once at the start avoids a failed upload on your first live order.

Custom formats on the Scale plan

If your carrier uses a non-standard column layout, requires specific field naming conventions, or expects a particular encoding or delimiter, the Scale plan lets you configure a custom carrier format to match those requirements exactly.
Navigate to Settings → Carrier Formats and select Add format. You can define the column order, header names, date formats, and field mappings that your carrier expects. Once saved, the format is available as an option when you download a CSV from any approved order.
Yes. If you work with more than one carrier — or if different order types need different formats — you can configure multiple named formats. At download time, you select which format to apply to that order.

Enterprise: automated delivery via ERP and API

On the Enterprise plan, the manual download step can be eliminated entirely. StackCube integrates directly with your ERP system or exposes an API endpoint that your logistics infrastructure can call to retrieve approved order data automatically.
Enterprise ERP and API integrations are configured during onboarding by the StackCube implementation team. Reach out to your account manager to scope your integration requirements and get the setup process started.
The carrier CSV reflects the order data exactly as it was at the moment of approval. If you need to correct an approved order before dispatch, contact your account team before uploading the CSV to your carrier. Re-downloading the file after an amendment ensures your carrier receives the corrected data.