Which provider new ICS shipments (ics-courier) are registered with. Applies within ~60 s (config cache). Existing shipments are not moved — use the migration below for those.

While this is on, every new customer ICS tracking number is additionally copied into the mirror account below and tracked there with the ICS module. Customer shipments keep their current provider and are never touched; mirrors send no alerts and use no capacity. Turn this off once the live provider above is switched to ICS module — the shadow copies are then redundant.

Mirrored shipments so far: —. Test connection asks the API server itself to call the ICS module — outbound access can differ per host. Backfill mirrors shipments that already exist (mirroring alone only catches new ones); run it repeatedly.

One entry per polling run against the ICS module. The hourly run only writes a shipment when something changed — an uneventful run leaves no trace in the shipment data, so this is the proof that it ran at all. A gap of more than one hour means the cron did not fire. Click any run to see every shipment it touched.

Moves all non-delivered ICS shipments onto the provider selected above: registers them at the target first, then flips their provider. Safe to run repeatedly — it only touches shipments not already on the target and skips any that fail to register (a re-run retries them).

Not yet on —: — shipments