BigCommerce and Marketplacer
Integration Agency & Consultants
Intelligent Consulting
Detailed Solution Design
Smooth Integration
Visibility
Training
BigCommerce
Common failures
Inventory latency and overselling
Operational impact: Delays in synchronising stock levels from Marketplacer sellers to the BigCommerce storefront result in selling stock that is not available. This forces the customer service team to cancel orders, damages customer trust, and creates payment reconciliation issues. At scale, this consistently undermines seller relationships and operational stability.
Prevention / Action: The integration must treat Marketplacer as the definitive source of truth for third-party inventory. Use webhook-driven updates for speed, but supplement this with a scheduled full stock synchronisation to ensure consistency. The integration logic must include robust queue handling and retry strategies to manage API rate limits or temporary outages without losing inventory updates.
Mismatched tax and shipping configurations
Operational impact: If BigCommerce checkout calculates shipping and tax using rules that are inconsistent with a seller's setup in Marketplacer, the final order total will be incorrect. This causes significant problems for the finance team during payout reconciliation, requiring manual adjustments to commissions and shipping fees. Incorrect totals can also cause orders to be rejected by seller systems, leading to fulfilment delays and CX overhead.
Prevention / Action: Establish a single source of truth for all shipping rates and tax logic before implementation. The integration must be designed to fetch and apply seller-specific costs from Marketplacer to the BigCommerce order before payment is captured. This requires a rigorous mapping of all seller shipping methods and tax rules, with a clear exception handling process for any unmapped scenarios.
Dispatch confirmation and tracking failures
Operational impact: A seller dispatches a Sales Order, but the tracking information from Marketplacer fails to update the corresponding order in BigCommerce. This leaves the order status as unfulfilled, prevents the customer from receiving their dispatch notification, and floods the CX team with preventable queries. It also means operational teams cannot effectively monitor seller fulfilment performance against SLAs.
Prevention / Action: Define a clear order state model that is mirrored across both systems. The integration must listen for shipment creation events in Marketplacer and be built to reliably update the BigCommerce order with the correct tracking number and carrier details. Implement monitoring with an exception queue for any failed dispatch updates, allowing an operations team to manually re-trigger the sync and ensure data consistency.
Disconnected returns and refund process
Operational impact: A refund processed in BigCommerce by the customer service team does not automatically trigger the corresponding return and refund workflow in Marketplacer. The finance team is left to manually reconcile payouts, commissions, and journals at month-end. Sellers are not correctly notified of the return, creating confusion around stock and financial reporting.
Prevention / Action: The returns process must be designed with a single point of initiation. If the customer service team must issue refunds from BigCommerce, the integration must capture that event and immediately trigger the corresponding 'Return Request' in Marketplacer. This ensures the seller's workflow is activated correctly and financial records are kept in sync automatically, avoiding manual intervention during financial close.
Frequently asked questions
How do we manage product information when adding hundreds of SKUs from new sellers?
Marketplacer serves as the master for third-party seller product data, including SKUs, descriptions, and pricing. This integration ensures that when a seller creates or updates an Item record in Marketplacer, it is automatically created or updated in the BigCommerce catalogue. This avoids the manual labour of exporting and importing product data, which often stalls marketplace launches.
What happens when a customer's basket contains products from our own warehouse and a third-party seller?
BigCommerce processes the full payment, but the integration must split the Sales Order for fulfilment. The third-party line items are sent to the correct seller via Marketplacer, while your own items follow your standard fulfilment workflow. A common failure is not synchronising this split-shipment logic, which prevents sellers from receiving their part of the order correctly.
How does the integration handle seller-specific information within BigCommerce if it's not a native feature?
Seller data is typically managed in Marketplacer and synchronised to the BigCommerce order using custom fields, sometimes called metafields. This process tags the order with the correct seller ID and any associated commission data from Marketplacer. Without this, it's impossible to automatically calculate seller payouts or route customer service queries effectively.
If BigCommerce handles checkout, how do we maintain control over shipping when sellers fulfil their own orders?
Your integration must correctly pass seller-specific shipping methods and costs from Marketplacer to the BigCommerce checkout. When an Item Fulfilment is created by the seller in Marketplacer, the tracking data must sync back to the original BigCommerce Sales Order. Failure to do this means customer service cannot answer tracking queries and the customer receives an inconsistent experience.