WooCommerce, Magento, BigCommerce & Other Platforms Guide

Purpose

This guide provides setup instructions for integrating various ecommerce platforms with EFS, including WooCommerce, Magento, BigCommerce, and other supported shopping carts. Each platform has unique requirements and configuration steps.

Table of Contents

Major Platforms (Detailed Instructions)

Additional Platforms (Quick Reference)

Order Management Systems

Legacy & Specialized Platforms

Universal Configuration

Before You Begin (All Platforms)

Universal Requirements

☐ EFS Account Setup

• Active FCP account with login credentials
• SKUs entered in FCP matching your platform’s SKUs
• Inventory received and in stock at EFS

☐ Integration Portal Access

• IS2 login credentials (request from Client Care if needed)
• URL: https://integration.efulfillmentservice.com

☐ Platform Access

• Admin access to your ecommerce platform
• Ability to generate API credentials (most platforms)
• Products listed with SKUs assigned

☐ Pre-Integration Tasks

• SKUs in platform match FCP SKUs exactly (or plan SKU mappings)
• Know your shipping method names (exact text)
• Have test products in stock for order testing

1. WooCommerce Setup

WooCommerce integrates using the WordPress REST API and requires generating API keys from your WordPress admin.

Prerequisites

WordPress Requirements:

• WooCommerce plugin installed and active
• WordPress permalinks set to anything OTHER than “Plain”
• Admin access to WordPress dashboard

To check permalinks:

1. Go to Settings → Permalinks in WordPress
2. Select any option except “Plain”
3. Click “Save Changes”

Step 1: Generate API Keys in WooCommerce

1. Log into your WordPress admin dashboard
2. Go to WooCommerce → Settings
3. Click the Advanced tab
4. Click REST API from the sub-menu
5. Click the “Add Key” button in the upper right

Configure the API key:

• Description: “EFS Integration” (or similar)
• User: Select an admin user
• Permissions: Select “Read/Write”
• Click “Generate API Key”

Important: Copy the Consumer Key and Consumer Secret immediately. You will NOT be able to see them again.

Step 2: Create Integration in IS2

1. Log into Integration Portal
2. Click “+ Add” button
3. Select WooCommerce from the dropdown

Fill out the configuration form:

Integration Name:

• One word, letters/numbers only, no spaces
• Example: “MyWooStore”

WMS Target:

• Should auto-populate with “FcpLive”

Order/Inventory Sync Schedule:

• Order Sync: Every 30 minutes (recommended)
• Inventory Sync: Hourly (recommended)

Store URL:

• Your store URL with trailing slash
• Example: https://www.my-store.com/
• Must include https:// or http://

Consumer Key:

• Paste the key from Step 1 exactly as shown

Consumer Secret:

• Paste the secret from Step 1 exactly as shown

Status of orders to pull:

• Default: “processing”
• This is the order status WooCommerce assigns to paid orders
• Only orders with this status will be retrieved

Order status when shipped:

• Default: “completed”
• Status we’ll set in WooCommerce when order ships

Tracking Plugin:

• Set to “No” unless you have WooCommerce Shipment Tracking plugin installed
• If using plugin, set to “Yes”

Step 3: Save and Test Connection

1. Click “Save Integration” button
2. Go to Cart Items section
3. Click “Refresh Cart Items” button

Success: Products from your WooCommerce store should appear in the list

Failure: If you see an error:

• Verify Store URL has correct format and trailing slash
• Check that Consumer Key and Secret are correct
• Confirm permalinks are not set to “Plain”

Step 4: Configure Ship Method Mappings

1. Go to Ship Maps section of your integration
2. Identify your WooCommerce shipping methods:
• Go to WooCommerce → Settings → Shipping in WordPress
• Note the exact name of each shipping method
3. Create mappings (see Section 16)

Common WooCommerce mappings:

• “Free shipping” → GROUND
• “Flat rate” → GROUND
• “Local pickup” → Hold for local pickup (or map to GROUND)

Step 5: Enable Sync and Test

1. Turn on Order Sync toggle
2. Turn on Inventory Sync toggle (optional)
3. Place a test order in your WooCommerce store
4. Verify order appears in IS2 Received Orders
5. Confirm order transfers to FCP

WooCommerce Notes

Product Status Filter:

• Integration only retrieves products with status “Publish”
• Draft products are ignored

Tracking Updates:

• Sent approximately 4 hours after shipment
• Order status changes to “completed” (or your configured status)
• If using Shipment Tracking plugin, tracking appears in plugin format

Inventory Sync:

• Updates stock quantities only
• Changes product stock status (in stock/backorder) based on quantity
• Syncs on configured schedule

2. Magento 2.x Setup

Magento 2.0+ uses OAuth for secure API connections. This integration requires creating an integration within Magento.

Prerequisites

Magento Version:

• Requires Magento 2.0 or higher
• For Magento 1.x, see Section 12

Admin Access:

• Ability to create integrations in Magento admin
• Admin user account

Step 1: Enable Magento API

1. Log into Magento admin panel
2. Go to System → Integrations
3. Click “Add New Integration”

Configure the integration:

Integration Info tab:

• Name: “EFS Fulfillment”
• Email: Your admin email
• Callback URL: Leave blank
• Identity Link URL: Leave blank

API tab:

• Resource Access: Select “Custom”
• Check the following permissions:
• Sales (all sub-items)
• Catalog → Products (all sub-items)
• Catalog → Inventory (all sub-items)
• Stores → Inventory Sources (if using multi-source inventory)

1. Click “Save”

Step 2: Activate Integration

1. After saving, find your new integration in the list
2. Click “Activate” link in the Actions column
3. Click “Allow” on the confirmation popup

Important: Copy all four tokens that appear:

• Consumer Key
• Consumer Secret
• Access Token
• Access Token Secret

Save these securely. You will NOT be able to see them again.

Step 3: Create Integration in IS2

1. Log into Integration Portal
2. Click “+ Add” button
3. Select Magento from dropdown

Fill out the configuration form:

Integration Name:

• One word, letters/numbers only
• Example: “MagentoStore”

WMS Target:

• Should auto-populate with “FcpLive”

Order/Inventory Sync Schedule:

• Order Sync: Every 30 minutes (recommended)
• Inventory Sync: Hourly (recommended)

Store URL:

• Your Magento store URL in format: https://www.yourstore.com/
• Must include https:// and trailing slash

Consumer Key:

• Paste from Step 2

Consumer Secret:

• Paste from Step 2

Access Token:

• Paste from Step 2

Access Token Secret:

• Paste from Step 2

History:

• Days of order history to check
• Recommended: 5 days
• Higher numbers slow down sync

Order Status:

• Status of orders to retrieve
• Default: “processing”
• Only orders with this status will be pulled

Store View ID:

• Optional: Enter specific store view ID if you have multiple store views
• Leave 0 for default/all store views
• Find Store View ID: Stores → All Stores in Magento admin

Set in/out of stock for each SKU:

• Yes: We’ll update stock status in Magento based on quantity
• No: We’ll only update quantities, not stock status

Notify customer that order shipped:

• Yes: Magento sends shipment email to customer
• No: No automatic email (you handle notifications)

Create invoice after updating tracking:

• Yes: Creates invoice in Magento when we add tracking
• No: No invoice created automatically

Capture payment for invoice:

• Yes: Captures payment when invoice created (requires “Create invoice” = Yes)
• No: Invoice created but payment not captured

Inventory Source:

• Optional: For Magento 2.4+ with multi-source inventory
• Enter the source code name exactly as in Magento
• Leave blank to use default source

Step 4: Save and Test Connection

1. Click “Save Integration” button
2. Go to Cart Items section
3. Click “Refresh Cart Items” button

Success: Products from Magento should load into the list

Failure: If error appears:

• Verify all four tokens are correct
• Check Store URL format (must have trailing slash)
• Confirm API permissions were granted correctly
• Re-generate tokens and try again

Step 5: Configure Ship Method Mappings

1. Go to Ship Maps section
2. Identify your Magento shipping methods
3. Create mappings for each method (see Section 16)

Step 6: Enable Sync and Test

1. Turn on Order Sync toggle
2. Turn on Inventory Sync toggle (optional)
3. Place test order in Magento
4. Verify order appears in IS2 and FCP
5. Confirm tracking updates return to Magento

Magento Notes

Tracking Updates:

• Tracking pushed approximately 4 hours after shipment
• Updates every 30 minutes at :20 and :50 minute marks
• Creates shipment record in Magento with tracking
• Optionally creates invoice and captures payment

Inventory Sync:

• Updates product quantities
• Optionally updates in stock/out of stock status
• Syncs to specified Inventory Source (2.4+) or default source
• Respects your sync schedule (hourly/daily/etc.)

Order Status Workflow:

• Orders pulled when status = “processing”
• We acknowledge receipt (optional status update)
• We create shipment and add tracking when shipped
• Order marked complete after shipping

3. BigCommerce Setup

BigCommerce uses API V3 with OAuth authentication for secure connections.

Prerequisites

Account Requirements:

• BigCommerce store (any plan supporting API access)
• Store owner or admin access

Step 1: Enable BigCommerce API

1. Log into BigCommerce admin
2. Go to Advanced Settings → API Accounts
3. Click “Create API Account”
4. Select “Create V2/V3 API Token”

Configure API Account:

Token Name:

• Enter: “EFS Integration”

OAuth Scopes: Set the following permissions to Read-Only or Modify:

• Orders: Modify
• Order Transactions: Read-Only
• Products: Modify
• Customers: Read-Only (optional)
• Store Information: Read-Only
• Shipping: Read-Only

All other scopes: None

1. Click “Save”

Important: Copy the following credentials immediately:

• Client ID
• Client Secret
• Access Token

You will NOT be able to view these again.

Step 2: Note Your Store Hash

On the API credentials screen, you’ll also see your API Path.

Example: https://api.bigcommerce.com/stores/{store_hash}/v3/

Copy the {store_hash} portion (the alphanumeric code).

Step 3: Create Integration in IS2

1. Log into Integration Portal
2. Click “+ Add” button
3. Select BigCommerce from dropdown

Fill out configuration form:

Integration Name:

• One word, letters/numbers only
• Example: “BigComStore”

WMS Target:

• Should auto-populate with “FcpLive”

Order/Inventory Sync Schedule:

• Order Sync: Every 30 minutes
• Inventory Sync: Hourly or twice daily

Store Hash:

• Paste the store hash from Step 2

Client ID:

• Paste from Step 1

Client Secret:

• Paste from Step 1

Access Token:

• Paste from Step 1

History:

• Days of order history to check
• Recommended: 5 days

Order Status to Pull:

• Default: “Awaiting Fulfillment”
• Only orders with this status will be retrieved

Order Status When Shipped:

• Default: “Shipped”
• Status we’ll set when order ships

Step 4: Save and Test Connection

1. Click “Save Integration” button
2. Go to Cart Items section
3. Click “Refresh Cart Items” button

Success: Products from BigCommerce load into list

Failure: If error:

• Verify Client ID, Secret, and Access Token are correct
• Confirm Store Hash is accurate
• Check API permissions include Orders (Modify) and Products (Modify)

Step 5: Configure Ship Method Mappings

1. Go to Ship Maps section
2. Identify BigCommerce shipping methods:
• Go to Store Setup → Shipping in BigCommerce admin
• Note exact name of each shipping method
3. Create mappings (see Section 16)

Step 6: Enable Sync and Test

1. Turn on Order Sync toggle
2. Turn on Inventory Sync toggle (optional)
3. Place test order
4. Verify order flow

BigCommerce Notes

Order Status:

• We retrieve orders with “Awaiting Fulfillment” status
• Order changes to “Shipped” when we add tracking
• Status names must match exactly (case-sensitive)

Tracking Updates:

• Sent approximately 4 hours after shipment
• Tracking added to BigCommerce order record
• Order status automatically updated

Inventory Sync:

• Updates inventory by variant/SKU
• Changes stock level at store level
• Respects sync schedule

Additional Platforms (Quick Reference)

This section covers setup for additional supported platforms. Each platform follows a similar general process but has unique requirements.

4. Wix

Wix integrates through our app available in the Wix App Market.

Prerequisites

Wix Requirements:

• Active Wix website with ecommerce enabled
• Wix site owner or admin access
• Products listed with SKUs

Setup Process

Step 1: Install EFS App

1. In your Wix dashboard, go to Apps → App Market
2. Search for “eFulfillment Service”
3. Click on the app and select “Add to Site”
4. Click “Add App” to confirm installation

Alternative: Visit https://www.wix.com/app-market/efulfillment-service

Step 2: Authenticate with IS2

1. After installation, you’ll be redirected to Integration Portal login
2. Enter your IS2 username and password
3. Click “Sign In”

Step 3: Configure Settings

Payment Status:

• Paid (recommended) – Only pull paid orders
• Unpaid – Pull all orders regardless of payment
• Pending – Pull orders with pending payment

Fulfillment Status:

• Not Fulfilled (recommended) – Pull unfulfilled orders only
• Partially Fulfilled – Pull partially fulfilled orders

Order Age:

• How many days back to check for orders
• Options: 3, 5, 7, or 14 days
• Recommended: 5 days

Interval to Retrieve Orders:

• How often we check for new orders
• Recommended: Every 30 minutes

Interval to Sync Inventory:

• How often we update inventory in Wix
• Recommended: Hourly

Step 4: Save Configuration

Click “Finish Setup” to complete installation.

Step 5: Configure Ship Method Mappings

1. In Integration Portal, go to your Wix integration
2. Click “Ship Maps”
3. Identify your Wix shipping methods:
• Go to Store Settings → Shipping in Wix dashboard
• Note the exact name of each shipping method
4. Create mapping for each method (see Section 16)

Step 6: Enable Sync

1. Turn on Order Sync toggle
2. Turn on Inventory Sync toggle
3. Place test order to verify

Wix Important Notes

⚠️ Order Editing Limitation:

Wix allows orders to be edited or canceled after fulfillment has been requested. However, Wix does NOT notify EFS of these changes.

This means:

• If you cancel an order in Wix after it’s been sent to EFS, we will NOT be notified
• The order will still be fulfilled unless you contact EFS directly
• We cannot be held responsible for orders fulfilled after Wix-side cancellation

Best practice: Contact EFS support immediately via ticket if you need to cancel an order that’s already been sent to our system.

Product Requirements:

• Products must have SKUs assigned in Wix
• SKUs must match FCP SKUs exactly
• Each variant needs its own SKU

Tracking Updates:

• Sent approximately 4 hours after shipment
• Order marked as fulfilled in Wix
• Tracking number added to order record

5. Squarespace

Squarespace integrates via API keys generated in your Squarespace settings.

Prerequisites

Squarespace Requirements:

• Squarespace Commerce plan (Business or higher)
• Site owner access
• Products with SKUs assigned

Setup Process

Step 1: Generate API Key in Squarespace

1. Log into your Squarespace site
2. Go to Settings → API Keys
3. Click “Create Key”
4. Key Name: “EFS” or “eFulfillment Service”
5. Scope: Ensure the following are checked:
• Orders – Read and Fulfill
• Inventory – Read and Write
6. Click “Create”

Important: Copy the API key immediately. You cannot view it again.

Step 2: Create Integration in IS2

1. Log into Integration Portal
2. Click “+ Add” button
3. Select Squarespace from dropdown

Configuration:

Integration Name:

• One word, letters/numbers only
• Example: “SquareStore”

WMS Target:

• Auto-populates with “FcpLive”

Order/Inventory Sync Schedule:

• Note: Squarespace does NOT support inventory syncing
• Order Sync: Every 30 minutes recommended

Access Token:

• Paste the API key from Step 1

History:

• Days of order history to check
• Options: 3, 5, 7, or 14 days
• Recommended: 5 days

Step 3: Save and Test

1. Click “Save Integration”
2. Go to Cart Items section

Important: Squarespace API does not provide product listings. You must manually add products.

Step 4: Add Products Manually

For each product EFS will fulfill:

1. In IS2 Cart Items section, click “+ Add Custom Item”
2. Item Name: Product description (for reference)
3. Item SKU: Must match EXACTLY as shown in Squarespace
• Find SKU: Commerce → Inventory in Squarespace
• Look in “Pricing & Variants” section
4. Click “+ Add”

Repeat for all products.

Step 5: Configure Ship Method Mappings

1. Go to Ship Maps section
2. In Squarespace, go to Store Settings → Shipping
3. Note exact names of your shipping methods
4. Create mappings (see Section 16)

Common Squarespace methods:

• “Default” → GROUND
• “Free Shipping” → GROUND
• “Express” → 2DAY

Step 6: Enable Order Sync

1. Turn on Order Sync toggle
2. Place test order
3. Verify order appears in IS2 and FCP

Squarespace Important Notes

No Inventory Sync:

• Squarespace API does NOT support inventory syncing
• You must manage inventory levels manually in Squarespace
• Or disable inventory tracking in Squarespace

Product SKUs:

• Critical that SKUs match exactly
• Each variant must have unique SKU
• Found in: Product → Pricing & Variants section

Order Status:

• We retrieve orders marked as unfulfilled
• Orders marked fulfilled manually in Squarespace will NOT sync tracking

Tracking Updates:

• Sent approximately 4 hours after shipment
• Order marked as fulfilled in Squarespace
• Tracking number and carrier added

6. Etsy

Etsy integrates using OAuth authentication through our Integration Portal.

Prerequisites

Etsy Requirements:

• Active Etsy shop
• Shop owner access
• Products with SKUs (optional but recommended)

Before Starting: You’ll need:

• Your Etsy shop name (found in Shop Manager sidebar)
• Your Etsy User ID (requires viewing page source – see below)

Setup Process

Step 1: Find Your Shop Name

1. Log into Etsy
2. Go to Shop Manager
3. Your shop name is displayed in the sidebar under “Sales Channels”
4. Write it down exactly as shown

Step 2: Find Your User ID

1. Click your profile icon (top right)
2. Select “View Profile”
3. On your profile page, right-click and select:
• Chrome: “View Page Source”
• Safari: “Show Page Source”
• Firefox: “View Page Source”
4. Press Ctrl+F (Cmd+F on Mac) to search
5. Search for: “data-user-id”
6. Copy the number that appears after it
• Example: data-user-id=”123456789″
• Your User ID is: 123456789

Step 3: Connect Through Integration Portal

1. Go to: https://integration.efulfillmentservice.com/integrations/connect/Etsy
2. If not logged in, enter your IS2 credentials
3. Click “Add New Etsy Integration”

Configuration Form:

Integration Name:

• One word, letters/numbers only
• Example: “MyEtsyShop”

WMS Target:

• Auto-populates with “FcpLive”

Order/Inventory Sync Schedule:

• Order Sync: Every 30 minutes
• Inventory Sync: Hourly or twice daily (optional)

Shop Name:

• Enter your Etsy shop name from Step 1
• Must match exactly

User ID:

• Enter the User ID from Step 2
• Numbers only

Step 4: Authorize Etsy Access

1. Click “Save Integration”
2. You’ll be redirected to Etsy
3. Log in to Etsy if prompted
4. Etsy will show permissions EFS is requesting:
• Read shop information
• Read and write orders
• Read and write listings (inventory)
5. Click “Allow Access”

You’ll be redirected back to Integration Portal.

Step 5: Verify Connection

Check that your integration shows:

• OAuth status: Connected
• Shop name displayed correctly

Step 6: Configure Ship Method Mappings

Etsy shipping methods depend on how you’ve configured your listings.

If using standard shipping:

• Etsy sends: “DOMESTIC” or “INTERNATIONAL”
• Create mappings for both

If using calculated shipping:

• Etsy sends the specific service name (e.g., “USPS First Class Mail”)
• Copy exact text from your Etsy listing
• Create mapping for each service

To find shipping method names:

1. Go to Shop Manager → Listings
2. Edit a listing
3. Scroll to Shipping section
4. Note exact names of shipping profiles/services

Create mappings in IS2 (see Section 16)

Step 7: Set Up Inventory Sync (Optional)

If you want inventory levels synced:

1. Important: You must have separate listings for each variant
• Example: Instead of “T-Shirt” with size options
• Create: “T-Shirt – Small”, “T-Shirt – Medium”, “T-Shirt – Large”
2. Each listing must have unique SKU matching FCP
3. Go to Cart Items in IS2
4. Activate products for syncing (click green play button)
5. Turn on Inventory Sync toggle

Step 8: Enable Sync and Test

1. Turn on Order Sync toggle
2. Place test order in Etsy
3. Verify order appears in IS2 and FCP
4. Confirm tracking returns to Etsy

Etsy Important Notes

SKU Matching:

• Etsy SKUs must match FCP SKUs exactly
• If no SKU in Etsy, we’ll use listing title (not recommended)
• Variants require unique SKUs for inventory sync

Inventory Sync Limitation:

• Only works with separate listings per variant
• Cannot sync variants within a single listing
• Consider if inventory sync is worth the listing structure change

Tracking Updates:

• Sent approximately 4 hours after shipment
• Order marked as shipped in Etsy
• Tracking number visible to buyer

Order Status:

• We retrieve orders marked “Paid” and “Not Shipped”
• Orders older than your history setting are ignored

7. eBay

eBay integrates using OAuth authentication through our Integration Portal.

Prerequisites

eBay Requirements:

• Active eBay seller account
• Business seller account recommended (not required)
• eBay Store subscription (not required but helpful)

Setup Process

Step 1: Connect Through Integration Portal

1. Log into Integration Portal
2. Click “+ Add” button
3. Select eBay from dropdown

Step 2: Configure Basic Settings

Integration Name:

• One word, letters/numbers only
• Example: “MyeBayStore”

WMS Target:

• Auto-populates with “FcpLive”

Order/Inventory Sync Schedule:

• Order Sync: Every 30 minutes
• Inventory Sync: Not Available

Marketplace Region:

• Select your eBay marketplace:
• US – eBay.com
• UK – eBay.co.uk
• Germany – eBay.de
• Canada – eBay.ca
• (and other regions)
• You need separate integration for each marketplace

History:

• Days of order history to check
• Options: 3, 5, 7, or 14 days
• Recommended: 5 days

Step 3: Save and Authorize

1. Click “Save Integration”
2. Click “Request OAuth Handshake” button (in integration settings)
3. You’ll be redirected to eBay
4. Log in to eBay if prompted
5. eBay shows permissions requested by EFS:
• Read and manage orders
• Read and update inventory
• Read shipping information
6. Click “Agree” to authorize

You’ll be redirected back to Integration Portal.

Step 4: Verify Connection

Check that OAuth fields are now populated:

• Access Token (grayed out field)
• Token Expiration (shows date)

Step 5: Refresh Cart Items

1. Go to Cart Items section
2. Click “Refresh Cart Items”

Success: eBay listings appear in the list

Step 6: Configure Ship Method Mappings

eBay shipping methods are based on what you’ve set in your listings.

Common eBay shipping services:

• “USPS Priority Mail”
• “USPS First Class”
• “FedEx Ground”
• “FedEx Home Delivery”
• “Standard Shipping”
• “Expedited Shipping”
• “Economy Shipping from outside US”

To find your specific methods:

1. Go to eBay Seller Hub
2. Review your active listings
3. Check shipping services offered
4. Note exact text

Create mappings in IS2 (see Section 16)

Step 7: Enable Order Sync and Test

1. Turn on Order Sync toggle
2. Create test order (or wait for real order)
3. Verify order appears in IS2 and FCP
4. Confirm tracking returns to eBay

eBay Important Notes

SKU Matching:

• Use eBay’s “Custom SKU” field (not Item Number)
• Custom SKU must match FCP SKU exactly
• Found when creating/editing listings under “Product Details”

Token Expiration:

• OAuth tokens expire periodically (typically every 18 months)
• You’ll receive notification when token is about to expire
• Re-authorize by clicking “Request OAuth Handshake” again

Tracking Updates:

• Sent approximately 4 hours after shipment
• Order marked as shipped in eBay
• Tracking visible to buyer
• Seller rating protected with valid tracking

Multiple Marketplaces:

• Each marketplace needs separate integration
• Example: Selling on eBay US and eBay UK = 2 integrations
• Each has its own OAuth authorization

Order Status:

• We retrieve orders marked “Paid”
• Orders marked as shipped manually in eBay will be ignored

8. Walmart

Walmart Marketplace integrates using API credentials generated in the Walmart Seller Center.

Prerequisites

Walmart Requirements:

• Active Walmart Marketplace seller account
• Approved seller status
• Products listed on Walmart Marketplace

Setup Process

Step 1: Generate API Credentials in Walmart

Important: Walmart API uses “delegated access” which must be set up correctly.

1. Log into Walmart Seller Center
2. Go to Settings (gear icon)
3. Navigate to API Access or Application Management
4. Click “Add New Application” or “Generate New Keys”
5. Follow Walmart’s delegated access setup process

Reference Walmart’s documentation: https://developer.walmart.com/doc/us/mp/us-mp-auth/

Required permissions:

• Orders: Read and Update
• Inventory: Read and Update
• Items: Read
• Shipping: Read and Update

Step 2: Obtain Client ID and Client Secret

After completing delegated access:

• Copy your Client ID
• Copy your Client Secret

Important: Save these securely. Treat them like passwords.

Step 3: Create Integration in IS2

1. Log into Integration Portal
2. Click “+ Add” button
3. Select Walmart from dropdown

Configuration:

Integration Name:

• One word, letters/numbers only
• Example: “WalmartStore”

WMS Target:

• Auto-populates with “FcpLive”

Client ID:

• Paste from Step 2

Client Secret:

• Paste from Step 2

Order Sync Schedule:

• Recommended: Every 30 minutes

Inventory Sync Schedule:

• Recommended: Hourly or every 2 hours

History:

• Days of order history to check
• Options: 3, 5, 7, or 14 days
• Recommended: 5 days

Step 4: Save and Test Connection

1. Click “Save Integration”
2. Go to Cart Items section
3. Click “Refresh Cart Items”

Success: Products from Walmart Marketplace appear in list

Failure: If error appears:

• Verify Client ID and Secret are correct
• Confirm API permissions were granted correctly
• Check that delegated access is properly configured
• Contact Walmart Seller Support if issues persist

Step 5: Configure Ship Method Mappings

Walmart uses standardized shipping methods:

Create mappings in IS2 (see Section 16)

Step 6: Set Up Inventory Sync

1. In Cart Items, activate products for syncing
2. Turn on Inventory Sync toggle
3. Inventory updates on your configured schedule

Step 7: Enable Order Sync and Test

1. Turn on Order Sync toggle
2. Place test order (or wait for real order)
3. Verify order flow through IS2 to FCP
4. Confirm tracking returns to Walmart

Walmart Important Notes

SKU Matching:

• Use Walmart’s “Product ID” or your custom SKU
• Must match FCP SKU exactly
• Case-sensitive

Tracking Requirements:

• Walmart has strict tracking upload requirements
• Late tracking can result in penalties
• Tracking sent approximately 4 hours after shipment
• Monitor closely for first week

Order Cancellation:

• Walmart allows customer cancellation up to certain point
• If order canceled after sent to EFS, contact support immediately
• Cannot hold Walmart responsible for late cancellation notices

Performance Metrics:

• Walmart monitors seller performance strictly
• Late shipments affect seller rating
• Ensure fulfillment latency is set appropriately
• Monitor order processing times

Inventory Sync:

• Updates inventory quantities in Walmart
• Critical for preventing overselling
• Walmart may suspend listings with frequent oversell issues

Platform Comparison Table

Quick reference for platform capabilities:

*Etsy inventory sync requires separate listings per variant

Universal Setup Tips

For All Platforms:

✓ Test thoroughly – Place test orders before going live
✓ Monitor initially – Check order flow daily for first week
✓ Set up notifications – Configure email alerts in FCP
✓ Document mappings – Keep record of ship method configurations
✓ Update promptly – Re-authorize OAuth if tokens expire

Common Issues Across Platforms:

• SKU mismatches (most common issue)
• Ship method not mapped
• OAuth token expiration
• Order status configuration incorrect
• Inventory tracking disabled in platform

Order Management Systems & Legacy Platforms

This section covers Order Management Systems (OMS) that aggregate orders from multiple channels, as well as legacy and specialized platforms.

9. ShipStation

ShipStation is an order management system that aggregates orders from multiple sales channels. Integration with EFS allows ShipStation to route orders to us for fulfillment.

Prerequisites

ShipStation Requirements:

• Active ShipStation account
• Admin access to generate API keys
• Orders flowing into ShipStation from your sales channels

Important: ShipStation integration does NOT support:

• Insurance value passthrough
• Signature required flag
• These must be added manually in FCP if needed

Setup Process

Step 1: Generate API Keys in ShipStation

1. Log into ShipStation
2. Click the gear icon (top right) for Settings
3. Go to Account → API Settings
4. If you already have API Key and Secret displayed:
• Copy them (skip to Step 2)
5. If no keys are displayed:
• Click “Generate New API Keys”
• Copy the generated Key and Secret

Important: API Keys provide full access to your ShipStation account. Keep them secure.

Step 2: Create Integration in IS2

1. Log into Integration Portal
2. Click “+ Add” button
3. Select ShipStation from dropdown

Configuration:

Integration Name:

• One word, letters/numbers only
• Example: “ShipStation”

WMS Target:

• Auto-populates with “FcpLive”

Order Sync Schedule:

• Recommended: Every 30 minutes
• ShipStation does NOT support inventory sync

API Key:

• Paste from Step 1
• Must match exactly (no spaces)

API Secret:

• Paste from Step 1
• Must match exactly (no spaces)

Order Tags:

• False (default) – Pull ALL orders from ShipStation
• True – Only pull orders tagged with “EFS” in ShipStation

Note: Order Tags feature allows you to selectively route orders if you have multiple fulfillment centers.

Step 3: Save and Test Connection

1. Click “Save Integration”
2. Go to Cart Items section
3. Click “Refresh Cart Items”

Success: Products from ShipStation appear in the list

Step 4: Configure Ship Method Mappings

ShipStation uses its own standardized shipping codes. Common mappings:

To find your ShipStation shipping methods:

1. Go to Settings → Shipping
2. Review configured carriers and services
3. Note exact names as they appear

Create mappings in IS2 (see Section 16)

Step 5: Optional – Configure Order Tags

If using Order Tags = True:

In ShipStation:

1. Go to Settings → Automation Rules
2. Create rule to tag orders destined for EFS
3. Add tag: “EFS” (exact match required)
4. Orders with this tag will be pulled by integration

Use case: You fulfill some orders yourself and route others to EFS.

Step 6: Enable Order Sync and Test

1. Turn on Order Sync toggle in IS2
2. Create test order in one of your ShipStation-connected stores
3. Verify order appears in ShipStation
4. Confirm order pulls into IS2 and FCP
5. Check that tracking returns to ShipStation

ShipStation Important Notes

No Inventory Sync:

• ShipStation integration does NOT support inventory syncing
• Inventory must be managed in your source platforms (Shopify, WooCommerce, etc.)

Order Status:

• We retrieve orders in “Awaiting Shipment” status
• After we ship, order marked as “Shipped” in ShipStation
• ShipStation then updates the source platform

Tracking Updates:

• Sent approximately 4 hours after shipment
• Tracking appears in ShipStation
• ShipStation automatically pushes tracking to source platforms

Insurance and Signature:

• These options NOT supported in integration
• If needed, manually edit order in FCP after it arrives
• Or contact support to add these options

Multi-Channel Use:

• ShipStation aggregates orders from all your stores
• All orders route through single EFS integration
• Use Order Tags if you need selective routing

10. Zentail

Zentail is a multi-channel ecommerce platform that manages inventory and orders across multiple marketplaces.

Prerequisites

Zentail Requirements:

• Active Zentail account
• Admin access
• Warehouse configured in Zentail (you’ll create this during setup)

Setup Process

Step 1: Add Integration in IS2

1. Log into Integration Portal
2. Click “+ Add” button
3. Select Zentail from dropdown

Configuration:

Integration Name:

• One word, letters/numbers only
• Example: “ZentailMain”

WMS Target:

• Auto-populates with “FcpLive”

Order/Inventory Sync Schedule:

• Order Sync: Every 30 minutes
• Inventory Sync: Hourly

Warehouse Unique ID:

• Leave blank for now (you’ll get this in Step 3)

Step 2: Save and Authorize

1. Click “Save Integration” button
2. You’ll be automatically redirected to Zentail for OAuth authorization
3. Log into Zentail if prompted
4. Click “Authorize & Install” to grant permissions

You’ll be redirected back to Integration Portal.

Important: Your integration now has an OAuth connection, but you still need to configure the warehouse in Zentail.

Step 3: Configure Warehouse in Zentail

1. Log into Zentail dashboard
2. Go to Account → Settings
3. Click “+ Create Warehouse”

Warehouse Configuration:

Warehouse Name:

• Enter: “EFS” (or any name you prefer)

Inventory Integration:

• Select: “eFulfillmentService (eFulfillment Service)”
• May show with number if you’ve authorized multiple times

Fulfill Integration:

• Select: “eFulfillmentService (eFulfillment Service)”
• Must be same integration as Inventory Integration

Step 4: Set Unique Identifier

1. Still in the warehouse settings page
2. Find fields:
• Shipping Integration Unique Identifier
• Inventory Integration Unique Identifier
3. Enter the SAME identifier in BOTH fields
• Example: “EFS1”
• Can be any text, but must be unique to this warehouse
• Must match exactly in both fields
4. Click “Update Warehouse”

Step 5: Complete IS2 Configuration

1. Return to Integration Portal
2. Go to your Zentail integration settings
3. Warehouse Unique Id: Enter the identifier from Step 4
• Must match exactly what you entered in Zentail
4. Access Token: Should already be populated from OAuth
5. Click “Save Integration”

Step 6: Verify Connection

1. In Zentail, assign some products to the EFS warehouse
2. Go to Cart Items in IS2
3. Click “Refresh Cart Items”

Success: Products assigned to EFS warehouse appear in list

Step 7: Configure Ship Method Mappings

Zentail uses the shipping methods configured in your source platforms (Amazon, eBay, Shopify, etc.).

1. Go to Ship Maps in IS2
2. Create mappings for common methods across all your channels
3. See Section 16 for details

Step 8: Enable Sync and Test

1. Turn on Order Sync toggle
2. Turn on Inventory Sync toggle
3. Place test order in one of your Zentail-connected channels
4. Verify order routes to EFS warehouse in Zentail
5. Confirm order appears in IS2 and FCP

Zentail Important Notes

Warehouse Assignment:

• Products must be assigned to EFS warehouse in Zentail
• Orders only route to EFS if product is in EFS warehouse
• Use Zentail’s warehouse logic to control routing

Unique Identifier Critical:

• Must be exactly the same in both Zentail fields
• Must match exactly in IS2 configuration
• Case-sensitive

Multi-Warehouse Support:

• Create multiple Zentail warehouses if you have multiple fulfillment centers
• Each needs separate EFS integration (if multiple EFS accounts)
• Or route to same EFS integration with different warehouse IDs

Inventory Sync:

• Updates from EFS back to Zentail
• Zentail then pushes to all connected channels
• Sync schedule applies to all channels

Order Sources:

• Orders come from all Zentail-connected platforms
• Single integration handles all sources
• Ship method depends on source platform

11. ChannelAdvisor

ChannelAdvisor is an enterprise-level multi-channel platform. Integration requires coordination with your Client Care Account Specialist.

Prerequisites

ChannelAdvisor Requirements:

• Active ChannelAdvisor account
• ProfileID for your account
• Admin access
• Distribution center configured in ChannelAdvisor

Setup Process Overview

⚠️ Important: ChannelAdvisor integration setup requires IT team involvement. You CANNOT complete this setup independently.

Step 1: Obtain ProfileID

1. Log into ChannelAdvisor
2. Go to My Accounts → Developer Network → Account Authorizations
3. Note your ProfileID (numeric value)
4. Copy this number

Note: If you have multiple accounts in ChannelAdvisor, each has its own ProfileID. You’ll need separate integration for each.

Step 2: Submit Setup Request

1. Create support ticket in FCP
2. Title: “ChannelAdvisor Integration Setup Request”
3. Include:
• Your ChannelAdvisor ProfileID
• Number of accounts to integrate
• Distribution center name you’ll use
• Preferred sync schedules

Step 3: EFS Triggers Developer Access Request

• EFS IT team will request developer access to your ChannelAdvisor account
• Request appears in: My Accounts → Developer Network → Account Authorizations
• You’ll see “eFulfillment Service” in pending requests

Step 4: Accept Developer Access

1. In ChannelAdvisor, go to pending developer requests
2. Find eFulfillment Service request
3. Click Accept in Actions column
4. Copy the AccountID that appears
5. Send AccountID to EFS via support ticket

Step 5: EFS Creates Integration

EFS IT team will:

• Create integration in Integration Portal
• Configure with your AccountID and ProfileID
• Set up distribution center connection
• Configure sync schedules per your preferences

You’ll be notified when complete.

Step 6: Configure Distribution Center

You must configure a distribution center in ChannelAdvisor:

Reference ChannelAdvisor documentation: http://ssc.channeladvisor.com/howto/inventory/settings/distribution-centers

Distribution Center settings:

• Name: “EFS” or “eFulfillment Service”
• Distribution Center Code: Provide to EFS via support ticket
• Associate with EFS integration

Step 7: Configure Item Labels (Optional)

If you want to limit which products EFS fulfills:

1. In ChannelAdvisor, create Item Label: “EFS”
2. Apply this label to products EFS should fulfill
3. Inform EFS via support ticket to filter by this label
4. Only products with “EFS” label will be retrieved

Step 8: Testing and Activation

Work with your Client Care Account Specialist to:

• Place test orders
• Verify order flow
• Confirm tracking updates
• Test inventory sync
• Approve go-live

ChannelAdvisor Important Notes

Enterprise Integration:

• Requires coordination with EFS IT team
• Cannot be self-service setup
• Allow 3-5 business days for setup

Distribution Centers:

• Required for proper routing
• Must provide distribution center code to EFS
• Orders route based on inventory location

Item Labels:

• Optional filtering mechanism
• Useful if selective routing needed
• Must apply labels in ChannelAdvisor before orders flow

ProfileID vs AccountID:

• ProfileID: Your ChannelAdvisor account number
• AccountID: Generated when you accept developer access
• Both are required for integration

Support:

• All ChannelAdvisor integration issues require support ticket
• Cannot troubleshoot independently
• Contact Client Care Account Specialist for assistance

12. Magento 1.x

Magento 1.x (versions 1.6-1.9) uses older SOAP API. This platform is legacy but still supported.

Prerequisites

Magento 1.x Requirements:

• Magento version 1.6 through 1.9
• SOAP services extensions for PHP (if self-hosted)
• Admin access to create API users

Note: For Magento 2.0+, see Section 2

Setup Process

Step 1: Create API Role in Magento

1. Log into Magento admin
2. Go to System → Web Services → Roles
3. Click “Add New Role” (top right)

Role Configuration:

• Role Name: “EFS Integration”
• In left menu, click Role Resources
• Check boxes for:
• Catalog
• Sales
• Catalog Inventory

1. Click “Save Role”

Step 2: Create API User

1. Go to System → Web Services → Users
2. Click “Add New User” (top right)

User Configuration:

• User Name: EFS
• First Name: Fulfillment
• Last Name: Integration
• Email: [email protected]
• API Key: Your EFS Merchant Token (from FCP)
• Found in FCP: Client Info → My Settings → Integration Credentials
• API Key Confirmation: Re-enter Merchant Token
• This account is: Active

1. In left menu, click User Role
2. Select radio button next to EFS Integration role
3. Click “Save User”

Step 3: Determine WSDL URL

Your WSDL URL format depends on hosting:

For self-hosted Magento:

https://www.yourstore.com/index.php/api/v2_soap/index/

For Magento Go:

https://storename.gostorego.com/api/v2_soap/index/

To verify correct URL:

• Open the URL in your browser
• You should see XML content starting with <definitions>
• If you see error or blank page, URL is incorrect

Step 4: Create Integration in IS2

1. Log into Integration Portal
2. Click “+ Add” button
3. Select Magento from dropdown

Configuration:

Integration Name:

• One word, letters/numbers only
• Example: “Magento1Store”

WMS Target:

• Auto-populates with “FcpLive”

Order/Inventory Sync Schedule:

• Order Sync: Every 30 minutes
• Inventory Sync: Twice daily

WSDL URL:

• Enter URL from Step 3
• Must be exact (include trailing slash)

User Name:

• Enter: EFS (if you followed Step 2)

User Password:

• Enter your EFS Merchant Token (from FCP)

History:

• Days of order history to check
• CRITICAL: Set to 5 days maximum
• Higher values cause slow/unstable communication

Skip SKUs not in control panel:

• No (recommended) – Orders with unknown SKUs will error
• Yes – Unknown SKUs will be removed from order
• ⚠️ Not recommended – causes slow sync speeds

Order Status:

• Status of orders to retrieve
• Default: “processing”
• Most common for paid orders ready to ship

Magento Shipment Email:

• Yes – Magento sends email when we add shipment
• No – No automatic email from Magento

Mark Order Shipped:

• Yes – Entire order marked complete when shipped
• No – Only fulfilled items marked shipped

Step 5: Save and Test Connection

1. Click “Save Integration”
2. Go to Cart Items section
3. Click “Refresh Cart Items”

Success: Products from Magento appear in list

Failure: If error appears:

• Verify WSDL URL is correct (test in browser)
• Confirm User Name is “EFS”
• Check User Password matches Merchant Token exactly
• Ensure API role has correct permissions

Step 6: Configure Ship Method Mappings

Magento shipping methods appear as text strings from your configured methods.

To find shipping methods:

1. In Magento admin, go to System → Configuration
2. Click Shipping Methods in left menu
3. Review enabled methods and their labels
4. Note exact text as displayed to customers

Create mappings in IS2 (see Section 16)

Step 7: Enable Sync and Test

1. Turn on Order Sync toggle
2. Turn on Inventory Sync toggle (optional)
3. Place test order
4. Verify order flow

Magento 1.x Important Notes

⚠️ Critical Settings:

• History must be 5 days or less – Higher values cause severe performance issues
• Do NOT use “Skip SKUs” feature – Causes slow sync speeds

API Credentials:

• User Password is your EFS Merchant Token (not Magento password)
• Found in FCP under Integration Credentials
• Must match exactly

WSDL URL Verification:

• Must end with /index/
• Test in browser before using
• Should display XML content

Order Status:

• Only orders matching configured status are retrieved
• “processing” is standard for paid orders
• Can customize based on your workflow

Tracking Updates:

• Create shipment record in Magento
• Add tracking number
• Optionally mark entire order complete
• Send Magento shipment email (if enabled)

Inventory Sync:

• Updates product quantity
• Can update product status (in stock/out of stock)
• Sync schedule should be conservative (twice daily max) to avoid performance issues

Performance:

• Magento 1.x SOAP API is slow compared to modern REST APIs
• Conservative sync schedules recommended
• Monitor for timeout errors

13. Volusion

Volusion is a hosted ecommerce platform that uses API access for integration.

Prerequisites

Volusion Requirements:

• “Pro” level account or higher (API access required)
• Admin access to generate API credentials
• Active Volusion store

Setup Process

Step 1: Generate API Credentials

1. Log into Volusion admin dashboard
2. Go to Inventory → Volusion API
3. Under “Generic” section, click “Run” next to Generic \ Orders

Configure column selection:

• Check the star (selects all fields)
• This ensures all order data is sent via API

1. Click purple “Run” button (top right)
2. A “Download” button appears, and to the right, a URL

Step 2: Extract API Components from URL

The URL will look like:
http://www.YOUR-STORE.com/net/[email protected]&EncryptedPassword=ABC123XYZ…&EDI_Name=Generic\Orders

Break down the URL:

• API URL: http://www.YOUR-STORE.com/net/WebService.aspx
• Login: [email protected]
• EncryptedPassword: ABC123XYZ… (long string of characters)

Copy each component separately.

Step 3: Create Integration in IS2

1. Log into Integration Portal
2. Click “+ Add” button
3. Select Volusion from dropdown

Configuration:

Integration Name:

• One word, letters/numbers only
• Example: “VolusionStore”

WMS Target:

• Auto-populates with “FcpLive”

Order/Inventory Sync Schedule:

• Order Sync: Every 30 minutes
• Inventory Sync: Twice daily (optional)

Login:

• Paste the login email from Step 2

Password:

• Paste the EncryptedPassword from Step 2
• This is NOT your Volusion account password
• It’s the encrypted password from the API URL

API URL:

• Paste the API URL from Step 2
• Format: http://www.YOUR-STORE.com/net/WebService.aspx
• Do NOT include the ? and parameters

Status:

• Order status to retrieve
• Common: “Ready to Ship”
• Can be any custom status you’ve created

Volusion Multi Store ID:

• Optional: Add prefix to order numbers if you have multiple Volusion stores
• Helps differentiate orders from different stores
• Example: “VOL1” creates order numbers like “VOL1-12345”
• Leave blank if single store

Step 4: Save and Test Connection

1. Click “Save Integration”
2. Go to Cart Items section
3. Click “Refresh Cart Items”

Success: Products from Volusion appear in list

Failure: If error:

• Verify API URL format is correct (no parameters after .aspx)
• Confirm Login email is exact
• Check Password is the EncryptedPassword (not account password)
• Ensure “Pro” level account with API access

Step 5: Configure Ship Method Mappings

Volusion shipping methods are defined in your store settings.

To find methods:

1. Go to Settings → Shipping
2. Review configured shipping methods
3. Note exact names

Create mappings in IS2 (see Section 16)

Step 6: Set Up Inventory Sync (Optional)

Volusion inventory sync updates product quantities.

1. In Cart Items, activate products for syncing
2. Turn on Inventory Sync toggle
3. Set conservative sync schedule (twice daily)

Step 7: Enable Order Sync and Test

1. Turn on Order Sync toggle
2. Place test order (or set existing order to “Ready to Ship” status)
3. Verify order appears in IS2 and FCP

Volusion Important Notes

Password Confusion:

• Password field requires EncryptedPassword from API URL
• NOT your Volusion account password
• Volusion generates encrypted password based on account password
• If you change Volusion password, you must update integration with new encrypted password

Order Status:

• Only orders matching configured status are retrieved
• “Ready to Ship” is most common
• You can use any custom status

Multiple Volusion Stores:

• Each store needs separate integration
• Use Multi Store ID to differentiate order numbers
• Helps prevent duplicate order number conflicts

Tracking Updates:

• Sent approximately 4 hours after shipment
• Order status changed to “Shipped”
• Tracking number added to order

API Access Limitation:

• Requires “Pro” level account or higher
• Lower tier accounts don’t have API access
• Contact Volusion if unsure about your account level

Password Changes:

• When you change your Volusion account password, the encrypted password changes
• You must update integration with new encrypted password
• Get new encrypted password by repeating Step 1-2

14. 3dCart

3dCart (now Shift4Shop) uses REST API for integration.

Prerequisites

3dCart Requirements:

• Active 3dCart/Shift4Shop store
• Admin access to create API app
• Store API enabled

Setup Process

Step 1: Enable REST API in 3dCart

1. Log into 3dCart admin
2. Go to Modules section
3. Find the REST API module
4. Enable the REST API module

Step 2: Add API App

1. After enabling REST API, you’ll need to add an APP
2. Click to add new app
3. Enter Public Key: 9efa495ae7489491ebe0bc11090186ed
• Copy/paste this exact key
4. Click “Save”

Step 3: Grant Permissions

Authorization window appears with permission requests:

Required permissions:

• Orders: Read and Write
• Products: Read and Write

Ensure both are set to Read and Write (should be default).

Click “Finish Setup”

Step 4: Enter FCP Settings

Another popup appears prompting for FCP settings:

Login Name and Password:

• Enter your FCP username and password

Order Filters and Order Status:

• Configure which orders to retrieve
• See “Order Status” section in 3dCart settings

Distributors & Dropshipping:

• Configure if using multiple fulfillment locations
• See “Distributors” section in 3dCart settings

Click to complete setup.

Step 5: Verify Connection

1. In FCP, go to Integration → View Integrations
2. Find your 3dCart integration
3. Click the “suitcase” icon to view cart items

Success: Products from 3dCart appear in searchable list with SKU match indicators

Failure: If error:

• Verify Public Key was entered correctly
• Check permissions include Orders and Products (Read/Write)
• Confirm FCP credentials are correct

Step 6: Configure Ship Method Mappings

1. In FCP, go to integration
2. Click “envelope” icon for shipping mappings
3. Note exact text of your 3dCart shipping methods
4. Create mappings (see Section 16)

Step 7: Optional – Configure Distributors

If using 3dCart’s Distributor feature for multiple fulfillment locations:

In 3dCart:

1. Go to Settings → General → Distributors
2. Create distributor entry for EFS
3. Note the Distributor ID (appears in URL when editing)
4. Associate products with EFS distributor

In FCP Integration:

• Enter the Distributor ID in integration settings
• Only items assigned to this distributor will be retrieved

Step 8: Configure Order Status

3dCart uses customizable order statuses.

To find status IDs:

1. Go to Settings → General → Order Status
2. Note the ID number next to each status name

In FCP Integration settings:

• Order Status ID: Status of orders to retrieve (typically “Ready to Ship”)
• Processing Status ID: Status to set when order is pulled
• Shipped Status ID: Status to set when order ships

Step 9: Enable Sync and Test

1. Sync should auto-enable after setup
2. Place test order
3. Verify order flow through integration

3dCart Important Notes

Product SKUs:

• Must be set in CODE column of Product Options
• Found in: Advanced Options section when editing product
• This CODE is the SKU passed to EFS

Variants:

• Each variant needs unique CODE (SKU)
• Set in Product Options section
• Parent product SKU not used for variants

Distributors:

• Useful for multi-warehouse setups
• EFS only retrieves orders for specified Distributor ID
• Other orders go to other fulfillment locations

Order Status:

• Customizable in 3dCart
• Must use status IDs (numbers), not names
• Status IDs visible in settings list

Tracking Updates:

• Sent approximately 4 hours after shipment
• Updates order status to “Shipped” (or configured status)
• Tracking visible to customer

Inventory Sync:

• Optional inventory sync available
• Can filter by country (pull only certain countries)
• Uses country codes (US, CA, MX, etc.)

Country Filtering:

• Optional feature to only pull orders from specific countries
• Comma-delimited list: “US,CA,MX”
• Leave blank to pull all countries

15. Other Platforms

Brief reference for additional supported platforms. For detailed setup, contact your Client Care Account Specialist.

AmeriCommerce

Setup Requirements:

• Generate API token in AmeriCommerce
• Get Store API URL
• Configure order and product statuses
• Optional: Warehouse ID for multi-warehouse

Key Notes:

• Requires admin user for API token
• Must have product status IDs
• Inventory sync optional

PrestaShop

Setup Requirements:

• Enable webservice in PrestaShop
• Generate webservice key
• Grant appropriate permissions
• May require Debug Mode (older versions)

Key Notes:

• Copy API key immediately (can’t view again)
• Requires specific permission settings
• Turn off Debug Mode after setup

InfusionSoft (Keap)

Setup Requirements:

• API key from InfusionSoft support
• Access URL (call InfusionSoft for this)
• Cannot update cart or sync inventory

Key Notes:

• “1-way” integration (retrieve orders only)
• No tracking updates back to InfusionSoft
• Product SKUs must match FCP exactly
• Can filter to paid invoices only

GeekSeller

Setup Requirements:

• GeekSeller username and password
• Optional: Market filtering

Key Notes:

• Aggregates orders from multiple marketplaces
• Can ignore specific markets (Amazon, eBay, etc.)
• Cart items must be added manually in IS2
• No product list retrieval from GeekSeller

PayPal (Shopping Cart)

Setup Requirements:

• Grant API permission to EFS
• Provide PayPal email address
• Set default shipping methods

Key Notes:

• Orders retrieved from last 72 hours
• API limit of 100 transactions per call
• High volume stores may miss orders
• Manual order entry recommended for backup
• Custom programming coordination required

BigCartel

⚠️ Beta Status:

• Integration is in beta
• Subject to bugs and changes
• Cannot add tracking numbers
• Manual updates only

Key Notes:

• Add SKU to end of product description (“SKU:YOURSKU”)
• Options combine with SKU (YOURSKU-SMALL)
• Shipping codes: DOMESTIC_DEFAULT / INTERNATIONAL_DEFAULT

QuickBooks Commerce (TradeGecko)

Setup Requirements:

• OAuth authorization through setup tool
• Stock location configuration
• Order status and fulfillment status settings

Key Notes:

• OAuth setup via dedicated URL
• Configure stock location in QB Commerce
• Set order age limit (recommended 5 days)

Platform Quick Reference Table

Universal Configuration & Troubleshooting

This section covers configuration steps that apply across all platforms, plus comprehensive troubleshooting guidance.

16. Ship Method Mapping Guide

Ship method mappings connect your platform’s shipping method names to EFS shipping codes. This is critical for proper order routing.

Understanding Ship Method Mappings

What they do:

• Translate your store’s shipping method text into EFS shipping codes
• Determine which carrier and service level we use to ship orders
• Control shipping costs and delivery times

Example:

• Customer selects: “2-Day Express Shipping” in your store
• Ship mapping translates this to: 2DAY
• EFS ships via: FedEx 2Day or UPS 2nd Day Air

How to Create Ship Mappings

Step 1: Identify Your Platform’s Shipping Methods

Find the exact text of your shipping methods:

For Shopify:

• Go to Settings → Shipping and delivery
• Review shipping profiles
• Note exact method names (case-sensitive)

For WooCommerce:

• Go to WooCommerce → Settings → Shipping
• Click each shipping zone
• Note method names exactly as shown

For Magento:

• Go to Stores → Configuration → Sales → Shipping Methods
• Review enabled methods and their labels

For marketplaces (Amazon, eBay, Walmart):

• Methods are standardized by platform
• See platform-specific sections for common methods

Important: Method names must match EXACTLY (case-sensitive, including spaces and punctuation).

Step 2: Access Ship Maps in IS2

1. Log into Integration Portal
2. Go to your integration
3. Click “Ship Maps” in the navigation menu

Step 3: Create a Mapping

1. Click “+ New Ship Map” button

Fill out the form:

Cart Method:

• Enter the shipping method name from your platform
• Must match exactly (case-sensitive)
• Example: “Standard Shipping” not “standard shipping”

WMS Shipping Code:

• Select from dropdown menu
• See EFS Shipping Codes table below

Signature Required (Optional):

• Check if this method requires signature on delivery
• Adds signature confirmation fee

Hold Orders (Optional):

• Select if orders with this method should be held for review
• Choose hold duration from dropdown
• Use for fraud prevention on high-value methods

Step 4: Save the Mapping

Click “Save” button at bottom of form.

Repeat for each shipping method in your store.

EFS Shipping Codes Reference

Domestic Ground Services:

USPS Services:

Express Services:

International Services:

Special Services:

Rate Shopping vs. Fixed Service

Rate Shopping Codes:

• “Best Rate” codes automatically select cheapest carrier
• We compare FedEx, UPS, and USPS rates in real-time
• Saves money on shipping costs
• May use different carriers for different orders

Recommended for:

• Free shipping offers
• Standard/economy shipping
• High-volume stores wanting cost savings

Fixed Service Codes:

• Specific carrier and service level
• Example: PRIORITY always uses USPS Priority Mail
• Consistent carrier for all orders with that method
• Predictable costs and transit times

Recommended for:

• Branded shipping (must be specific carrier)
• When specific service features needed
• Subscription boxes requiring consistent experience

Common Mapping Examples

E-commerce Store Mappings:

“Free Shipping” → Best Rate Economy Lightweight Post

“Standard Shipping” → Best Rate Economy Lightweight Post

“Ground Shipping” → GROUND

“Priority Shipping” → PRIORITY

“2-Day Shipping” → 2DAY

“Express Shipping” → 2DAY

“Overnight Shipping” → OVERNIGHT

“International Shipping” → INTERNATIONAL_DEFAULT

“International Express” → INTERNATIONAL_PRIORITY

Marketplace Mappings:

Amazon:

Standard → Best Rate Economy Lightweight Post

Expedited → 2DAY

NextDay → OVERNIGHT

SecondDay → 2DAY

International → INTERNATIONAL_DEFAULT

eBay:

USPS Priority Mail → PRIORITY

USPS First Class Mail → FIRST_CLASS

FedEx Ground → GROUND

FedEx 2Day → 2DAY

Standard Shipping → Best Rate Economy Lightweight Post

Special Mapping Scenarios

Scenario 1: Local Pickup

If you offer local pickup and don’t want orders shipped:

Option A – Hold for pickup:

• Map to: HOLD
• Order appears in FCP but won’t ship
• You must arrange pickup with customer

Option B – Map to ground and handle manually:

• Map to: GROUND or any shipping code
• Monitor for local pickup orders in FCP
• Cancel/hold manually before fulfillment

Scenario 2: Free Shipping with Threshold

If you offer free shipping over certain dollar amount:

• Map “Free Shipping” method to: Best Rate Economy Lightweight Post
• System doesn’t differentiate between free shipping and paid shipping
• Both use same shipping code

Scenario 3: Tiered Shipping Speeds

If you offer multiple speeds at different prices:

“Standard (3-5 days)” → Best Rate Economy Service

“Express (2-3 days)” → PRIORITY

“Rush (1-2 days)” → 2DAY

Scenario 4: International Regions

Some platforms allow different international methods by region:

“International Standard” → INTERNATIONAL_DEFAULT

“Canada Shipping” → INTERNATIONAL_DEFAULT

“Europe Express” → INTERNATIONAL_PRIORITY

“Asia Expedited” → INTERNATIONAL_EXPRESS

EFS automatically routes to appropriate carrier based on destination country.

Testing Ship Method Mappings

After creating mappings:

Step 1: Place Test Orders

Create test order for EACH shipping method:

• Use real address (your own)
• Select specific shipping method
• Complete checkout

Step 2: Verify in FCP

1. Check order in FCP after it syncs
2. Go to Orders → Search/Edit Orders
3. Find test order
4. Click order number to view details
5. Check Shipping Service field shows correct EFS code

Step 3: Confirm Correct Service

• GROUND orders should show FedEx/UPS Ground
• PRIORITY orders should show USPS Priority Mail
• 2DAY orders should show 2-Day Air service
• Etc.

If wrong service appears:

• Check cart method name matches EXACTLY
• Verify spelling, capitalization, spacing
• Re-create mapping with correct cart method text

Updating Existing Mappings

To edit a mapping:

1. Go to Ship Maps section
2. Find the mapping to edit
3. Click the edit icon (pencil)
4. Make changes
5. Click “Save”

To delete a mapping:

1. Find the mapping
2. Click the delete icon (trash can)
3. Confirm deletion

Important: Deleting a mapping doesn’t affect existing orders, only future orders.

Ship Method Mapping Best Practices

Do:

• ✓ Create mappings for ALL shipping methods offered
• ✓ Test each mapping with actual order
• ✓ Use rate shopping codes when possible to save costs
• ✓ Document your mappings for reference
• ✓ Review mappings when adding new shipping options

Don’t:

• ✗ Leave shipping methods unmapped (causes order errors)
• ✗ Use special characters in method names if possible
• ✗ Create multiple mappings for same cart method
• ✗ Change platform method names after creating mappings
• ✗ Assume mappings work without testing

Unmapped Shipping Methods

What happens if method is unmapped:

1. Order syncs from platform to IS2
2. IS2 can’t find mapping for shipping method
3. Order gets IMPORT ERROR status in IS2
4. Error message: “Ship method not mapped”
5. Order does NOT transfer to FCP

To fix:

1. Check Received Orders log in IS2 for error details
2. Note the exact cart method name from error
3. Create ship mapping for that method
4. Order will retry on next sync cycle (30 minutes)
5. Or manually re-submit order through IS2

17. Inventory Sync Setup

Inventory syncing keeps your platform’s stock levels updated with your actual EFS inventory, preventing overselling.

How Inventory Sync Works

The process:

1. Order ships from EFS
• Inventory decreases in FCP
• Example: 100 units → 99 units
2. Sync schedule triggers
• Based on your configured schedule (hourly, daily, etc.)
• IS2 checks for inventory changes since last sync
3. IS2 pushes update to platform
• Sends new quantity for each SKU
• Example: Update Product ABC to 99 units
4. Platform updates inventory
• Stock level changes in your store
• Customers see updated availability

Frequency: Depends on your configured schedule

Direction: One-way only (EFS → Platform)

• We push inventory TO your platform
• We do NOT pull inventory FROM your platform
• Platform inventory changes don’t affect EFS

Enabling Inventory Sync

Step 1: Choose Sync Schedule

Common options:

• Hourly – Good for high-volume stores
• Twice Daily – Balanced approach
• Daily – Low-volume or slow-moving inventory
• Manual Only – You trigger syncs on-demand

Consider:

• How quickly inventory turns over
• How important real-time accuracy is
• API rate limits on your platform

Step 2: Configure in Integration Settings

1. Go to your integration in IS2
2. Find Inventory Sync Schedule setting
3. Select frequency from dropdown
4. Save integration

Step 3: Activate Products for Sync

Not all products need syncing. Activate only products you want synced:

1. Go to Cart Items section
2. Find products to sync
3. Click the green “Play” button in Options column
4. Status changes to ACTIVE

Or activate in bulk:

1. Select multiple products (checkboxes)
2. Click bulk action button
3. Select “Activate for Sync”

Step 4: Enable Inventory Sync Toggle

1. Return to integration main page
2. Find Inventory Sync toggle switch
3. Turn to ON (blue)

Inventory sync is now active.

What Gets Synced

Synced:

• ✓ Available quantity (from “Good” inventory in FCP)
• ✓ In stock / Out of stock status (based on quantity)
• ✓ For each activated product/SKU

NOT synced:

• ✗ Hurt bin inventory (damaged items)
• ✗ Product pricing
• ✗ Product descriptions or images
• ✗ Product weight or dimensions
• ✗ Variants or options structure

Platform-Specific Inventory Sync Notes

Shopify:

• Syncs to the EFS app location only
• Must have products stocked at app location
• Updates inventory by variant SKU
• Updates tracked quantity only (doesn’t change tracking status)

WooCommerce:

• Updates “_stock” field
• Changes stock status (instock/outofstock) if quantity hits zero
• Syncs to simple and variable products

Magento:

• Can sync to specific source (Magento 2.4+ MSI)
• Updates quantity and stock status
• Can configure whether to update stock status or quantity only

BigCommerce:

• Updates inventory level by variant
• Changes stock status based on quantity
• Syncs to store-level inventory

Amazon:

• Updates fulfillment quantity for MFN listings
• Does NOT affect FBA listings (separate inventory)
• Can sync to specific marketplace only

Etsy:

• Only works with separate listings per variant
• Cannot sync variants within single listing
• Updates quantity and renew status

eBay:

• API does NOT support inventory sync
• Must manage inventory manually in eBay

Squarespace:

• API does NOT support inventory sync
• Must manage inventory manually in Squarespace

ShipStation:

• OMS does NOT support inventory sync
• Inventory must sync to source platforms (Shopify, WooCommerce, etc.)

Manual Inventory Sync

You can manually trigger inventory sync anytime:

1. Go to your integration in IS2
2. Find Inventory Sync section
3. Click “Sync Now” or “Force Sync” button
4. Confirmation message appears

Use manual sync when:

• Testing inventory sync setup
• Major inventory change occurred
• Discrepancy needs immediate correction
• Regular schedule isn’t frequent enough

Inventory Sync Troubleshooting

Issue: Inventory not syncing to platform

Check:

1. Is Inventory Sync toggle ON?
2. Are products activated (green play button)?
3. Does product SKU match exactly between FCP and platform?
4. Is sync schedule configured?
5. Check Last Sync timestamp – is it recent?

Issue: Wrong quantity syncing

Check:

1. Verify you’re looking at “Good” inventory in FCP (not total)
2. Check if product has multiple locations (correct location syncing?)
3. Confirm no manual inventory adjustments made in platform
4. Review Inventory Activity Report for unexpected changes

Issue: Some products sync, others don’t

Check:

1. Are all products activated in Cart Items?
2. Do all SKUs match exactly?
3. Check if some products are variants (need parent SKU or variant SKU?)
4. Review sync logs for specific error messages

Issue: Sync happening too slowly

Solutions:

• Increase sync frequency (hourly instead of daily)
• Reduce number of products syncing
• Check platform API rate limits
• Contact support if persistent

Inventory Buffer Strategy

Some merchants prefer keeping a buffer between actual inventory and displayed inventory:

Why use buffer:

• Protects against overselling during sync delays
• Allows time to restock before showing out of stock
• Prevents selling last unit during fulfillment

How to implement:

Option 1: Adjust in platform

• Manually set platform inventory slightly lower than actual
• Example: 100 units in FCP, set 95 in platform
• Requires manual management (not recommended)

Option 2: Low stock threshold

• Set low stock alerts in FCP
• Reorder when reaching buffer level
• Don’t let inventory hit zero

Option 3: Safety stock setting

• Some platforms allow “safety stock” or “reserve quantity”
• Check platform documentation

Recommendation: Most merchants sync actual inventory and rely on frequent sync schedule rather than buffer.

Best Practices for Inventory Sync

Do:

• ✓ Start with conservative sync schedule (daily or twice daily)
• ✓ Increase frequency as you verify reliability
• ✓ Test sync with low-risk products first
• ✓ Monitor for first week after enabling
• ✓ Activate only products EFS fulfills
• ✓ Keep SKUs consistent across all platforms

Don’t:

• ✗ Sync too frequently (can hit API limits)
• ✗ Manually adjust inventory in both places
• ✗ Assume sync is instant (delays are normal)
• ✗ Activate products EFS doesn’t fulfill
• ✗ Change SKUs after sync is configured

18. Troubleshooting Common Issues

Comprehensive troubleshooting for integration problems across all platforms.

Orders Not Syncing From Platform

Symptom: Orders placed in platform don’t appear in IS2 or FCP.

Troubleshooting steps:

1. Verify Order Sync is enabled

• Go to integration in IS2
• Check Order Sync toggle is ON (blue)
• If OFF, turn it ON

2. Check order status in platform

• Order must match configured status
• Example: If integration set to pull “processing” orders, order must be “processing”
• Verify payment was successful (most integrations only pull paid orders)

3. Wait for sync cycle

• Syncs occur on schedule (typically every 30 minutes)
• Check “Last Sync” timestamp in IS2
• Wait for next sync cycle before troubleshooting further

4. Review platform-specific requirements

Shopify:

• Product must be at app location
• Automatic fulfillment must be enabled
• Product must request fulfillment

WooCommerce:

• Order status must be “processing” (or configured status)
• Product SKU must exist

Magento:

• Order must have configured status
• Product must be assigned to correct source (MSI)

Amazon:

• Must be Seller-Fulfilled (not FBA)
• Order must be unshipped
• Product must be in Cart Items list

5. Check Received Orders log

• Go to integration → Received Orders
• Look for order with error status
• Read error message for specific issue

6. Verify integration connection

• Check OAuth status (if applicable)
• Re-authorize if token expired
• Test connection by refreshing cart items

7. Check History setting

• If order is older than history setting, won’t be retrieved
• Example: History = 5 days, order from 7 days ago won’t sync
• Adjust history setting if needed (don’t exceed recommended limits)

Orders in IS2 But Not FCP

Symptom: Order appears in IS2 Received Orders but doesn’t transfer to FCP.

Troubleshooting steps:

1. Check order status in IS2

• Go to Received Orders log
• Find the order
• Look at status column

Status meanings:

• NEW – Waiting to transfer to FCP (normal, will transfer soon)
• ACCEPTED – Successfully transferred to FCP
• IMPORT ERROR – Problem transferring (see error message)

2. If status is IMPORT ERROR:

Common error messages and solutions:

“Ship method not mapped”

• Create ship mapping for that shipping method
• See Section 16 for mapping instructions
• Order will retry automatically on next sync

“SKU not found”

• Product SKU in platform doesn’t match FCP SKU
• Check spelling, capitalization, spaces
• Add product to FCP or create SKU mapping in Cart Items

“Address validation failed”

• Customer address is incomplete or invalid
• Edit order in platform to fix address
• Or manually enter order in FCP with corrected address

“Customer information missing”

• Name, email, or phone missing from order
• Edit order in platform to add information
• Or manually enter in FCP

“Duplicate order”

• Order with same number already exists in FCP
• Check if order already fulfilled
• May be test order conflicting with real order

3. If status is stuck on NEW:

• Wait 30 minutes (normal transfer delay)
• If still NEW after 2 hours, contact support
• Provide order number from platform and IS2

4. Check for special characters

• Some characters in names/addresses cause issues
• Review order for apostrophes, accents, symbols
• Edit in platform if possible

5. Manually submit order

• In IS2 Received Orders, find order
• Click “Resubmit” or “Force Import” button
• System will attempt transfer again

Tracking Not Updating in Platform

Symptom: Order ships from EFS but tracking doesn’t appear in your platform.

Troubleshooting steps:

1. Verify timing expectations

• Tracking uploads occur ~4 hours after shipment
• Updates batch process at :20 and :50 past the hour
• Allow up to 6 hours from shipment time

2. Check order status in IS2

• Go to Received Orders
• Find the order
• Check status

Expected status: COMPLETED (means tracking was sent) If not COMPLETED: Tracking hasn’t been sent yet

3. Verify tracking in FCP

• Log into FCP
• Go to Orders → Search/Edit Orders
• Find order (should be brown “Completed” status)
• Verify tracking number exists
• Confirm order actually shipped

4. Check platform-specific issues:

Shopify:

• Verify fulfillment wasn’t manually marked complete
• Check app location is still connected
• Ensure fulfillment service wasn’t removed

Amazon:

• Verify order is still in seller account (not removed by Amazon)
• Check fulfillment latency hasn’t expired
• Confirm order wasn’t canceled by buyer

eBay:

• Check OAuth token hasn’t expired
• Verify listing is still active
• Confirm order wasn’t marked shipped manually

General platforms:

• Ensure API credentials still valid
• Check for platform maintenance or outages

5. Look for error messages

• In IS2 Received Orders, expand order details
• Look for tracking update error messages
• Common issues: API timeout, permission denied, order locked

6. Manual tracking update

• If tracking won’t auto-update, add manually
• Go to platform and add tracking number
• Found in FCP order details
• Copy/paste tracking number and select carrier

Inventory Not Syncing

Symptom: Inventory changes in FCP don’t reflect in your platform.

Troubleshooting steps:

1. Verify inventory sync enabled

• Check Inventory Sync toggle is ON
• Verify sync schedule is configured
• Check Last Sync timestamp

2. Verify products activated

• Go to Cart Items in IS2
• Check products have ACTIVE status (green play button)
• If showing as inactive, click play button to activate

3. Verify SKU matching

• Product SKU in platform must match FCP SKU exactly
• Case-sensitive
• Check for extra spaces or characters

4. Check platform limitations:

Squarespace: No inventory sync support (API limitation) ShipStation: No inventory sync (manage in source platforms) InfusionSoft: No inventory sync (one-way integration)

5. Check sync frequency

• If sync is daily, inventory only updates once per day
• Check Last Sync time to see when next sync will occur
• Manually trigger sync to test immediately

6. Platform-specific checks:

Shopify:

• Verify product is at app location
• Check inventory is tracked at app location
• Ensure product variants have correct SKUs

WooCommerce:

• Confirm “Manage stock” is enabled for product
• Check product isn’t draft/private

Magento:

• Verify correct inventory source configured (MSI)
• Check product is assigned to that source

7. Review sync logs

• Some platforms show sync logs or errors
• Look for “permission denied” or “product not found” errors

8. Manual sync test

• Manually trigger inventory sync
• Change quantity in FCP
• Force sync
• Check if platform updates

SKU Mismatch Errors

Symptom: Orders error due to SKU not found or mismatch.

Solutions:

Option 1: Fix SKU in Platform (Recommended)

1. Identify correct SKU from FCP
2. Edit product in platform
3. Update SKU to match FCP exactly
4. Save changes
5. New orders will use correct SKU

Option 2: Fix SKU in FCP

1. Go to FCP → Client Info → View Items
2. Find product
3. Click Edit
4. Update SKU to match platform
5. Save

Caution: This affects all integrations and internal systems

Option 3: Create SKU Mapping (For Bundles)

Use when 1 platform SKU = multiple FCP SKUs:

1. Go to Cart Items in IS2
2. Find the platform product
3. Click “+ Add SKU Map”
4. Add each FCP SKU and quantity
5. Save mapping

Example:

• Platform SKU: “GIFTSET”
• Maps to:
• FCP SKU “ITEM-A” Qty 1
• FCP SKU “ITEM-B” Qty 2
• FCP SKU “ITEM-C” Qty 1

Option 4: Add Product to FCP

If product truly missing from FCP:

1. Go to FCP → Client Info → Items
2. Click “Add New Item”
3. Enter SKU matching platform
4. Complete product details
5. Save

OAuth Token Expired

Symptom: Integration stops working, error mentions authentication or authorization.

Solution:

For platforms using OAuth:

• Shopify
• Magento 2
• BigCommerce
• Etsy
• eBay
• Amazon
• Zentail

Re-authorize integration:

1. Go to integration settings in IS2
2. Look for “Authorize” or “Re-authorize” button
3. Click button
4. You’ll be redirected to platform login
5. Log in
6. Grant permissions again
7. Redirect back to IS2

Check for:

• Button may say “Request OAuth Handshake”
• May need to save integration first
• Follow same process as initial setup

Token expiration timeline:

• Most platforms: 18 months
• Some platforms: 90 days
• You should receive expiration warning email

Address Validation Issues

Symptom: Orders error due to address validation failures.

Common causes:

• Apartment/suite number missing
• PO Box when carrier doesn’t deliver to PO Boxes
• Invalid city/state/zip combination
• International address in wrong format
• Special characters in address fields

Solutions:

1. Edit address in platform

• Go to order in your platform
• Edit shipping address
• Correct issues
• Save
• Order will retry on next sync

2. Manually enter order in FCP

• If order can’t auto-correct
• Create new order manually in FCP
• Use corrected address
• Include original order number in notes

3. Contact customer

• If address appears wrong
• Contact customer to verify
• Get corrected address
• Update order

4. Common corrections:

• Add apartment number
• Spell out street abbreviations (St → Street)
• Remove special characters
• Verify zip code matches city/state

Duplicate Orders

Symptom: Same order appears multiple times in FCP.

Common causes:

• Order synced multiple times due to platform status changes
• Test order not deleted before real order
• Manual entry plus automatic sync
• Integration configured multiple times

Prevention:

1. Don’t manually fulfill in platform

• Let integration handle fulfillment status
• Manual changes can cause re-sync

2. Delete test orders

• Remove test orders from platform before going live
• Or use different product SKUs for tests

3. Check for multiple integrations

• Review integrations list in IS2
• Delete duplicates or old test integrations
• Keep only one active integration per platform

Resolution:

If duplicate already in FCP:

1. Identify which order is correct (usually first one)
2. Go to duplicate order in FCP
3. Change status to “Canceled”
4. Add note: “Duplicate order”
5. Original order processes normally

Platform-Specific Error Messages

Shopify Error: “Fulfillment request not found”

• Product not at app location
• Move product inventory to app location

WooCommerce Error: “Consumer Key invalid”

• API key was regenerated or deleted
• Create new API key and update integration

Magento Error: “Access denied”

• API permissions insufficient
• Re-check integration permissions in Magento
• Ensure all required scopes granted

Amazon Error: “Invalid marketplace”

• Marketplace region setting incorrect
• Verify marketplace in integration settings matches account

BigCommerce Error: “Store hash invalid”

• Store hash changed or incorrect
• Re-copy store hash from API settings

eBay Error: “Token expired”

• OAuth token needs renewal
• Re-authorize integration

When to Contact Support

Contact EFS support if:

• ✓ You’ve tried troubleshooting steps without success
• ✓ Error messages are unclear or technical
• ✓ Integration was working but suddenly stopped
• ✓ Orders are time-sensitive and need immediate resolution
• ✓ You suspect issue is on EFS side
• ✓ Platform not listed in guides

How to contact support:

Support Ticket (Recommended):

1. Log into FCP
2. Go to Client Info → Support
3. Create ticket
4. Include:
• Platform name
• Integration name in IS2
• Order number (platform and FCP if applicable)
• Error messages (copy exact text)
• Screenshots of issue
• Steps you’ve already tried

Email: [email protected]

Phone: 1-866-922-6783 (Press 2 for Customer Service)

For integration setup assistance: Contact your Client Care Account Specialist

Integration Maintenance Checklist

Weekly:

• ☐ Review Received Orders log for errors
• ☐ Spot-check that orders are flowing correctly
• ☐ Verify tracking updates returning to platform
• ☐ Check inventory sync accuracy (if enabled)

Monthly:

• ☐ Review ship method mappings (any new methods added?)
• ☐ Check OAuth token expiration dates
• ☐ Test order flow with actual order
• ☐ Verify all products still syncing correctly
• ☐ Review integration settings for changes needed

When Adding New Products:

• ☐ Ensure SKUs match between platform and FCP
• ☐ Add to Cart Items in IS2 if needed
• ☐ Activate for inventory sync if desired
• ☐ Test order with new product

When Changing Shipping Options:

• ☐ Create new ship method mappings
• ☐ Test orders with new methods
• ☐ Update documentation

After Platform Updates:

• ☐ Verify integration still working
• ☐ Check for any new API requirements
• ☐ Test order flow
• ☐ Update settings if needed

Additional Resources

Integration Portal: https://integration.efulfillmentservice.com

EFS Support Site: http://support.efulfillmentservice.com

Platform Documentation:

• Shopify: https://help.shopify.com
• WooCommerce: https://woocommerce.com/documentation
• Magento: https://docs.magento.com
• BigCommerce: https://support.bigcommerce.com
• Amazon: https://sellercentral.amazon.com/help
• eBay: https://developer.ebay.com

Related EFS Guides:

• Bulk Upload CSV Guide (alternative order submission)
• API Integration Guide (custom development)
• FCP Quick Reference (manual order entry)

Congratulations!

You’ve completed the comprehensive WooCommerce, Magento, BigCommerce & Other Platforms integration guide. Your integration should now be properly configured and orders flowing smoothly between your platform and EFS.

For ongoing support, reference this guide and contact your Client Care Account Specialist with any questions.