Once CloudX is installed and configured (see 01 - Setting up CloudX), most flows run automatically. This article covers day-to-day operations, the two optional mapping features that tune what TRAEDE sends, and how to uninstall.

What happens automatically

• Releasing a shipment with a CloudX shipping method pushes it to CloudX as a Pick Ticket.
• CloudX marks the Pick Ticket as shipped once the warehouse ships it. TRAEDE picks that up on its next poll and updates the shipment's status.
• Once every 5 minutes, TRAEDE polls CloudX for receiving ticket updates and imports received / cancelled quantities back onto the matching production order delivery note.
• Every night at 03:00 (Copenhagen time), TRAEDE pushes the full product catalog to CloudX Style Master.
• Every night at 03:30, TRAEDE pulls stock levels from CloudX for the mapped warehouses and updates inventory.

Everything below is either operator-triggered or a configuration knob you set once.

Sending a shipment to CloudX

1. Create a shipment as normal on an order.
2. Set the Shipping method to a method with code type CloudX.
3. Release the shipment. TRAEDE pushes it to CloudX as a Pick Ticket.

The shipment's sync status changes to Synced once CloudX confirms it received the Pick Ticket. If CloudX rejects it, the status changes to Error and the reason appears on the shipment page.

When the warehouse ships the parcel, CloudX reports it back and TRAEDE marks the shipment as shipped. Tracking numbers are imported at the same time.

Note: A successful push only means CloudX queued the Pick Ticket for ingestion. Rare late failures — where CloudX rejects a ticket after accepting it — are caught on TRAEDE's next background check and surface as an error on the shipment.

Sending a production order (ASN) to CloudX

Production order pushes are always operator-triggered so you can review the delivery note first.

1. Open the production order.
2. Open the delivery note you want to send as an ASN.
3. Make sure the delivery note has an Expected delivery date. CloudX requires it.
4. Click Push to CloudX in the sidebar.

Once the warehouse counts the goods and posts them to inventory, CloudX reports the received quantities back. TRAEDE writes them onto the delivery note automatically and updates the production order status.

Note: The supplier on the production order must have a primary address with a valid two-letter state code (for example CA, NY, DK). CloudX's ASN schema rejects anything else, so TRAEDE checks it up front and tells you which supplier to fix.

Order type mapping

CloudX validates the orderType field on every Pick Ticket against a per-tenant list of accepted values (for example WEB, WHOLESALE, RETAIL, DROPSHIP). Ask your CloudX contact which values your tenant accepts.

By default TRAEDE omits the field, in which case CloudX applies its own default. To send a specific value, go to the Order type section under Settings:

1. Set a Default order type — used whenever no row below matches.
2. Optionally, add per-order-type mappings. Each row maps a TRAEDE order type (b2b, b2c, consignment, proposal) to a CloudX order type. Matching rows win over the default.
3. Save.

Custom field mapping

CloudX exposes several free-form fields on Pick Tickets and Receiving Tickets — customerPONumber, billingOption, shipViaAccountNumber, startDate, cancelDate on Pick Tickets; customerPO on Receiving Tickets. TRAEDE only populates these fields when you map them to one of your custom fields.

How to add a mapping

1. Open the Settings tab and scroll to Custom field mapping.
2. Under Pick tickets (outbound) or Receiving tickets (inbound), click Add mapping.
3. Pick the CloudX field to populate.
4. Pick the TRAEDE custom field that holds the value. Pick tickets read from order custom fields; receiving tickets read from production order custom fields.
5. Save.

Notes on specific fields

• startDate and cancelDate fall back to today's date when the mapped custom field is empty on an order, so a Pick Ticket always ships with dates set.
• billingOption must map to a TRAEDE select custom field whose option values match CloudX's PickTicketBillingOption enum (FreightCollect, ThirdParty, ConsigneeBill, Prepaid, Sender, Recipient, CollectBilling). Any other value is dropped from the payload rather than being sent as an invalid string.

On-demand actions

The Actions section runs jobs immediately rather than waiting for the nightly schedule.

Diagnostics

The Diagnostics tab lets you hit CloudX with each region's client secret to confirm OAuth and connectivity. A successful call also returns the list of warehouses that tenant has configured — use those exact codes when filling in the warehouse mapping.

Limitations

• Returns are not synced back to CloudX. Handle them via TRAEDE's return portal and register the credit note in TRAEDE.
• Products without a UPC (EAN) are skipped by the Style Master push. Set a UPC on the variant before pushing shipments that reference it.
• Pick Ticket cancellations only succeed while the ticket is in a pre-shipping state on CloudX. Once the warehouse has picked or generated a label, CloudX will reject the cancellation and TRAEDE surfaces the rejection reason.

Uninstalling

1. Go to App Store → CloudX → Settings.
2. Scroll to the bottom and click Uninstall.
3. Confirm.

Uninstalling clears all client secrets, warehouse mappings, and other CloudX settings in TRAEDE. Data already sent to CloudX stays on the CloudX side.

Related articles

• 01 - Setting up CloudX — install and initial configuration