ParcelPilot
Help

BigCommerce

This guide covers what ParcelPilot needs to connect to BigCommerce, where to find it in BigCommerce, and where to enter it in ParcelPilot.

What ParcelPilot needs

From a BigCommerce Store-level API account (V2/V3 API Token):

  1. Store Hash
  2. Access Token
  3. Client ID
  4. Client Secret

Where to find it in BigCommerce

Create a Store-level API account

  1. BigCommerce Admin → Settings → API Accounts
  2. Go to Store-level API accounts
  3. Click Create API Account
  4. Token type: V2/V3 API Token
  5. Name: ParcelPilot

Permissions / scopes

For import-only (read-only), enable:

  • Orders → Read-only
  • Products → Read-only
  • Information & settings → Read-only

If later you want ParcelPilot to push tracking back to BigCommerce, you may need additional write permissions (only enable what you need).

Download the credentials file

After saving, BigCommerce downloads a .txt file with values like:

  • ACCESS TOKEN
  • CLIENT ID
  • CLIENT SECRET
  • API PATH (e.g. https://api.bigcommerce.com/stores/XXXXXXXX/v3/)

Store Hash is the XXXXXXXX part of the API PATH after /stores/.

Where to enter it in ParcelPilot

ParcelPilot Admin → Integrations → Client Integrations → create/edit an integration with Platform = BigCommerce.

Fill these fields:

  • Store Hash → credentials.bigcommerce.store_hash
  • Access Token → credentials.bigcommerce.access_token
  • Client ID → credentials.bigcommerce.client_id
  • Client Secret → credentials.bigcommerce.client_secret

Operational settings:

  • Push shipment confirmations (tracking) back to ecommerce platform → settings.push_ship_confirms

Product Data / Units

BigCommerce now uses the shared Product Data / Units section for product weight handling.

  • Auto-detect or use store default keeps the existing behavior: ParcelPilot infers the store-level weight unit from the BigCommerce store metadata during product sync.
  • Fixed override stores a shared weight-unit override at settings.product_units.weight_mode = fixed and settings.product_units.weight_unit.

ParcelPilot records the resolved source alongside the imported weight metadata so operators can distinguish an inferred store unit from a fixed override.

Troubleshooting

401 / 403 errors

  • Confirm the store hash matches the API PATH.
  • Confirm scopes/permissions are sufficient.
  • Regenerate the API account and retry.

Missing orders?

If orders are missing in ParcelPilot, you can manually backfill using Pull Orders on the integration:

Security notes

  • Treat Access Token and Client Secret as sensitive.
  • Use read-only permissions unless you explicitly need write access.

See also