01 - Setting up CloudX

  • Updated

CloudX is a warehouse management system used by several 3PL operators across the US and UK. This integration syncs products, shipments and inventory between TRAEDE and the warehouse, pushes ASNs on inbound production orders, and imports back shipment confirmations and receipts.

A single install covers both regions. Provide the client secret for each region you plan to use; leave the other empty if only one region is active.

Prerequisites

Before you install, gather the following from your CloudX contact:

  • An OAuth2 client secret for each region (US and/or UK) your brand ships from.
  • The CloudX warehouse code for every warehouse you want TRAEDE to talk to. You can also fetch these later from the Diagnostics tab once installed.

You should also decide which TRAEDE inventory location will represent each CloudX warehouse. If the location does not exist yet, create it first under Settings → Inventory settings → Inventory locations.

Install the app

  1. Go to App Store → CloudX in the left menu.
  2. Open the Install tab.
  3. Enter the US client secret, the UK client secret, or both. At least one is required.
  4. Click Install.

Important: Client secrets cannot be edited later from the Settings tab. If you need to add, remove, or rotate a secret, uninstall the app and reinstall it. Uninstalling clears the warehouse mapping and other settings, so you will need to reconfigure them.

Map warehouses

The warehouse mapping tells TRAEDE which CloudX warehouse belongs to which TRAEDE inventory location. No flow reaches CloudX until this mapping is filled in.

  1. Open the Settings tab.
  2. In the Warehouse mapping section, click Add mapping.
  3. Pick the TRAEDE inventory location.
  4. Pick the Region (US or UK). This decides which client secret is used at runtime.
  5. Pick the CloudX warehouse from the dropdown. The list is fetched from CloudX using the region's client secret.
  6. Add one row per warehouse you want to use.

Tip: If the CloudX warehouse dropdown says None available — set region secret and retry via Diagnostics, the region's client secret was not entered at install time. Uninstall, reinstall with the missing secret, and try again.

Enable sync options

Every flow is off by default so nothing reaches CloudX until you explicitly enable it. In the Sync options section, tick only the flows you need.

Option What it does
Push shipments (Pick Tickets) to CloudX Releasing a shipment that uses a CloudX shipping method automatically pushes it to CloudX as a Pick Ticket.
Push products (Style Master) to CloudX Enables the nightly catalog push (03:00 Copenhagen time) and the manual Push products now action. Products are pushed to CloudX Style Master keyed by UPC (EAN); variants without a UPC are skipped.
Push production orders (Receiving Tickets / ASNs) to CloudX Enables the Push to CloudX button on each production order delivery note. No automatic push — always operator-triggered.
Import receipt updates from CloudX Every 5 minutes, polls CloudX for receiving ticket updates and imports received or cancelled quantities back onto the matching production order delivery note in TRAEDE.
Sync inventory from CloudX (only mapped locations) Enables the nightly inventory sync (03:30 Copenhagen time) and the manual Sync inventory now action. Pulls stock levels from CloudX and updates TRAEDE inventory for the mapped warehouses.

Important: Only enable Sync inventory from CloudX once you have confirmed that inventory in CloudX is accurate. TRAEDE will overwrite the mapped locations with whatever CloudX reports.

Set up a CloudX shipping method

Shipments only push to CloudX when the shipping method they use has its code type set to CloudX. Create one method per carrier / service level the warehouse should honour.

  1. Go to Settings → Shipping methods.
  2. Click Create shipping method (or open an existing one).
  3. Set the Code type to CloudX.
  4. Set the Code to the CloudX Ship Via value (for example UPS EU for a UK tenant). This is the carrier the warehouse will use.
  5. Set the Ship service field to the CloudX service level (for example UPS Standard). Both fields are mandatory on CloudX's pick-ticket payload.
  6. Save.

Save

Click Save settings at the bottom of the Settings tab. The integration is now active for every flow you enabled.

Optional tuning steps — order type mapping, custom field mapping, and day-to-day operations — are covered in the next article.

Related articles

Was this article helpful?

0 out of 0 found this helpful