Carrier CSV export#

After approval, StackCube can generate carrier-ready CSV files so the operations team does not rebuild upload sheets by hand.

StackCube carrier CSV download control — The order queue keeps carrier-format download actions close to approved and rejected orders so exports stay intentional.

What export uses#

Carrier export uses approved order data:

Recipient name
Phone number
Address
Item summary
Quantity
Delivery note
Sender or warehouse details

Only approved orders should be exported.

If order-specific sender information is blank, StackCube may use the default sender fields from Shipping/Carrier settings. Update these defaults whenever the fulfillment warehouse changes.

StackCube shipping sender defaults — The Settings shipping tab manages default sender name, phone, and address for carrier files.

Setup steps#

Choose the first carrier format.
Confirm required columns and field order.
Map StackCube order fields to carrier fields.
Export sample approved orders.
Upload to the carrier system and confirm acceptance.

Before Download#

If selected orders are missing required shipping fields, review the warning before downloading. Missing recipient name, phone, or address can cause carrier upload failure or misdelivery.

Edit shipping information in order detail, then download again. Because the same order can be exported multiple times, operations should track which downloaded file was actually uploaded to the carrier.

Custom Columns#

Adjust download columns when a carrier or warehouse requires a specific header or order. Start from the default format and add only the fields needed to fix real upload errors.

Common carriers#

Teams commonly request formats for CJ Logistics, Lotte, Hanjin, or custom warehouse upload files. Custom formats depend on plan and onboarding scope.

Export control#

Keep export permission limited to users responsible for fulfillment. Re-exporting should be intentional so duplicate shipments are avoided.