Connect BigCommerce as a fulfillment destination, map products and push only the intended orders.

1. Prepare BigCommerce credentials

1. Sign in to the correct BigCommerce store with permission to manage API accounts.
2. Open Settings → Store-level API accounts.
3. Create a dedicated API account for this integration.
4. Set Orders: Modify and Products: Read-Only, as requested by the current PledgeBox form.
5. Save and retain the generated Access Token securely.

Find the Store Hash in the API path or store control-panel URL. In https://store-example123.mybigcommerce.com, the example hash is example123. Use your own store’s hash.

BigCommerce API-account documentation

2. Connect PledgeBox

1. Open Dashboard → Push to Fulfillment.
2. Click Add a New Fulfillment.
3. Select BigCommerce.
4. Enter Store Hash and Access Token.
5. Check the destination store and click Save & Next.
6. Complete product or SKU mapping in the following steps.

Enter the token only in the integration’s credential field. Do not include it in screenshots, order notes or support messages.

3. Push and verify orders

1. Filter the orders you intend to send.
2. Check completion, balance, address, quantities and SKU mappings.
3. Check whether those orders have already been pushed.
4. Review the order count before confirming the push.
5. Review the PledgeBox result and verify the orders in BigCommerce.

For a later batch, use the connection’s new-push workflow where available. Recheck the filters and previous results to avoid duplicates.

General fulfillment workflow · SKU filters