Operations resources

Prepare the process before connecting the technology.

Use these implementation checklists to expose the order, product, carrier and exception decisions a reliable rollout needs.

Implementation checklist

Six conversations worth having before go-live.

These are practical planning prompts, not claims about unreleased product capabilities.

01

Map the order sources

List each store, marketplace, structured file and manual source. Record who owns credentials, what order state should import and how duplicates are prevented.

  • Source and store owner
  • Import timing and eligibility
  • Reference and duplicate rules
02

Prepare dispatch data

Identify which products lack the weight, dimensions, packaging or listing match needed to select a service and book successfully.

  • Weights and dimensions
  • Pack and variant rules
  • Unmatched listing process
03

Document service decisions

Turn the decisions operators make today into explicit priorities, zones, schedules, rate cards and allowed manual overrides.

  • Destination and weight bands
  • Service priorities
  • Exception ownership
04

Test carrier accounts

Use representative shipments to verify credentials, required fields, references, label output and provider-specific limitations.

  • Credentials and environments
  • Services and formats
  • Failure and retry process
05

Define the daily controls

Agree which workload and exception signals the team will check before dispatch starts and during the day.

  • Due and overdue orders
  • Unmatched data
  • Booked and dispatched work
06

Include reverse movements

Treat returns, exchanges, collections and third-party movements as designed workflows rather than afterthoughts.

  • Return locations
  • Approved services
  • Customer communication
Buying questions

Ask what happens when the happy path fails.

  1. Can the team correct customer, address or product data before booking?
  2. Which carrier actions are genuinely supported for each account?
  3. Can automated service selection be overridden by an authorised operator?
  4. Where do shipment references and labels remain visible?
  5. How are uninstall, privacy, tenant access and credential storage handled?
Talk to us

Bring the current process, including the awkward exceptions.

We will map the channels, carrier accounts, order volume and warehouse decisions that matter before proposing an implementation.