ParcelPilot
Help

Client Integrations — Create, Edit & Delete

Use Client Integrations to connect a client to an eCommerce platform so ParcelPilot can import data and (optionally) push tracking/fulfilment updates back.

Create a client integration

  1. Go to Integrations → Client Integrations.
  2. Click Create.
  3. Select the Client.
  4. Choose the Platform.
  5. Enter the required credentials and settings.
  6. Enable the integration.
  7. Click Create.

Tip: the page header includes platform-specific help actions that point to the setup details for the selected platform.

Actions

Platform-specific help actions are available on the create/edit form:

  • BigCommerce setup (help icon on the “BigCommerce credentials” section)
  • Shopify integration help
  • WooCommerce integration help
  • Magento integration help

These open in-app setup notes, permissions/scopes, and platform-specific requirements.

Edit a client integration

  1. Open the integration.
  2. Update credentials/settings as needed.
  3. Click Save.

Notes:

  • Credentials and settings are encrypted at rest.
  • If you rotate API keys, update them here.

Shared order workflow policy

For ecommerce integrations, the main workflow control is now Order workflow policy.

This shared policy is designed to work across Magento, Shopify, WooCommerce, BigCommerce, Amazon, Mirakl, eBay, TikTok, Etsy, and NOTHS so operators do not have to think in a different way for each platform.

It splits behaviour into five decisions:

  • Import: should ParcelPilot create/update the order locally?
  • Reservation: should the order reserve stock?
  • Processing: should the warehouse be allowed to pick, pack, and ship it?
  • Lifecycle: what should happen when the upstream order becomes completed/cancelled, or when an operator removes it locally?
  • Retention: should completed/cancelled orders be kept for accounting, audit, or GDPR reasons?

For the retention and anonymisation details behind those lifecycle and GDPR settings, see:

There is also a Go-live transition section for onboarding and history imports:

  • ParcelPilot fulfilment start date: the date the warehouse actually starts fulfilling this client's ecommerce orders in ParcelPilot.
  • Import pre-go-live orders as read-only history: imports older upstream orders for search, returns, finance, and audit visibility while keeping them out of warehouse work queues.

When an order is marked as pre-go-live history, ParcelPilot automatically blocks shipment-confirmation pushback for that order.

For cancelled orders, that means the policy can keep the record while still ensuring ParcelPilot removes live warehouse demand from unshipped allocations and reservations.

Presets

The fastest way to configure a client is to start with one of the built-in presets:

  • Warehouse fulfilment: import live operational orders, keep on-hold orders visible, reserve only real warehouse demand, and block completed/cancelled orders from processing.
  • Accounting and history: import completed orders as read-only records for finance export or reconciliation, without sending them into the warehouse queue.
  • Cancelled audit only: keep cancelled history for investigations, stock audits, or customer-support tracing.

Legacy platform sections

Magento and WooCommerce still show older platform-specific controls for backwards compatibility.

  • Magento: the old allow-list still exists, but the shared workflow policy should now be the main source of truth.
  • WooCommerce: old pull-status filters can still be used as an API-side fetch optimisation, but the shared workflow policy should decide live behaviour inside ParcelPilot.

Virtual bundle stock sync

Ecommerce integrations also include a separate stock-sync setting for virtual bundle parent quantities:

  • Enable virtual bundle parent stock sync

This setting stores settings.bundle_stock_sync.enabled and is:

  • default-off
  • only meaningful when stock sync is enabled
  • only meaningful when Stock master is ParcelPilot

When enabled, ParcelPilot can append derived parent bundle quantities for supported fixed virtual bundles to outbound stock payloads. It does not change warehouse reservation or fulfilment behavior.

Recommended operating model

For most clients:

  • import operational orders
  • optionally import on-hold orders for visibility
  • do not reserve or process completed or cancelled orders by default
  • keep completed orders only when accounting/history needs them
  • keep cancelled orders only when audit/support needs them

For onboarding or migration projects with historical imports:

  • set the ParcelPilot fulfilment start date before the first backfill
  • enable Import pre-go-live orders as read-only history if older marketplace orders still need to be searchable in ParcelPilot
  • leave those orders visible for history, but do not let them reserve stock, create shipments, or push fulfilment back upstream

That gives a cleaner warehouse queue and avoids “why did this order come back?” confusion.

Delete a client integration

  1. Open the integration.
  2. Use Delete.

Before deleting, consider disabling instead (so history remains intact).

Related guides