WooCommerce

This guide covers what ParcelPilot needs to connect to WooCommerce (WordPress), where to find it, and where to enter it in ParcelPilot.

What ParcelPilot needs

1. Store URL (your website base URL)
2. Consumer Key (WooCommerce REST API key)
3. Consumer Secret (WooCommerce REST API secret)

Where to find it in WooCommerce

Create REST API credentials

1. Log in to WordPress Admin
2. Go to WooCommerce → Settings → Advanced → REST API
3. Click Add key
4. Set:
   • Description: ParcelPilot
   • User: a dedicated technical/admin user (recommended)
   • Permissions:
     • Use Read for import-only setups
     • Use Read/Write if ParcelPilot needs to update order status / push shipment tracking
5. Click Generate API key
6. Copy:
   • Consumer key
   • Consumer secret

Important: WooCommerce will only show the secret once.

Where to enter it in ParcelPilot

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

Fill these fields:

• Store URL → credentials.woo.store_url (e.g. https://store.example.com)
• Consumer Key → credentials.woo.consumer_key
• Consumer Secret → credentials.woo.consumer_secret

Operational settings:

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

Notes & tips

• Make sure the site uses HTTPS.
• Some security plugins or WAF rules can block REST API calls; whitelist ParcelPilot if needed.
• If you use Cloudflare, ensure it’s not challenging API requests.

Troubleshooting

401 Unauthorized / 403 Forbidden

• Confirm the key permissions are correct (Read vs Read/Write).
• Confirm the WooCommerce REST API is enabled.
• Try generating a new key for a dedicated user.

REST API endpoint errors

• Confirm the Store URL is the WordPress site root (not /wp-admin).
• Confirm permalinks are enabled in WordPress.

Missing orders?

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

• Pull Orders from eCommerce (manual backfill)

Security notes

• Treat Consumer Key/Secret as credentials.
• Rotate keys if they’re exposed.