How to Integrate Concierge With Non-Shopify Platforms

Concierge works with all of Zest's supported ecommerce platforms: Shopify, Magento, BigCommerce, Commerce 7, and Salesforce Commerce Cloud. If your store is on a different platform, there's a quick and easy path to get you up and running.

This article covers everything you need to know about connecting Concierge to a non-Shopify platform, from initial setup to day-to-day operations.

Zest Concierge works with the following ecommerce platforms. All plan tiers are supported.

If your store is on a platform Zest doesn't natively support — like WooCommerce, Squarespace, Wix, or a fully custom tech stack — reach out to the Zest team for integration steps.

Zest creates orders in Magento via the standard Magento REST API. Each order arrives with a Pending Zest status, which you can customize — for example, to Processing - Admin — to distinguish Zest orders from regular web orders in your reports and fulfillment rules.

Zest populates all standard Magento order fields, including:

When a Concierge order is fully discounted, Zest always populates line item totals with the pre-discount price to ensure downstream systems (such as SAP or your ERP) calculate correctly.

If your Magento instance uses Amasty or other third-party order attribute extensions, Zest writes those attributes in a separate step after order creation. If orders ever get stuck following a Magento platform update, contact your success manager — this is usually resolved quickly.

Scheduled delivery dates are stored in the appropriate Magento order attribute so they flow through your existing ERP and fulfillment workflows without any additional configuration.

Assigning a custom order status (such as Processing - Admin) to Zest orders makes it easy to filter them in reports and set up separate fulfillment rules.

Order syncs typically complete within about 5 minutes. Zest doesn't use a static IP address, so no firewall allowlisting is required on your side.

If the API connection drops or orders fail to push, Zest retries automatically at increasing intervals. Most temporary issues — like a platform maintenance window — resolve without any manual action. If orders remain stuck in Pending Zest status after the underlying issue is resolved, contact your success manager.

Your Magento API credentials added to Zest remain intact during a version update, so no Zest reconfiguration is needed. That said, custom integrations (such as order attribute writing) can occasionally be affected by a Magento-side deploy. Verify gifting functionality after any platform updates and report any issues to your success manager promptly.

When generating your BigCommerce API credentials for Zest, grant the following permissions:

Create separate API credentials for your sandbox and production environments.

Zest populates the following fields when creating orders in BigCommerce:

BigCommerce's API restricts writing to the Payment Status field — this is a BigCommerce platform limitation, not a Zest limitation. Zest cannot populate this field regardless of API permissions.

If another system (such as NetSuite) also writes to BigCommerce's External Order ID field after an order is created, Zest may need to use an alternative field to store the Zest order ID. Contact your success manager if this applies to your setup.

BigCommerce blocks order creation when a product is out of stock with the message: "Quantities of one or more products are out of stock or did not meet quantity requirements." Zest cannot bypass this check. To unblock affected orders:

Hiding a product's visibility in BigCommerce does not affect Zest's ability to create orders. Only actual inventory availability matters.

BigCommerce has a separate Purchasable flag on product variants that controls whether a variant can be ordered, independently of inventory count. This is sometimes used for limited-time or made-to-order items. If a variant's Purchasable flag is turned off, Zest cannot create orders for it even if inventory shows as available. Update this flag directly in BigCommerce to unblock.

BigCommerce enterprise plans have no practical rate limits for Zest's usage. BigCommerce uses real-time webhooks, so order status and inventory updates are reflected quickly.

Zest uses the Salesforce Commerce APIs (SCAPI) to create and manage orders. Each Zest environment connects to one Salesforce Commerce Cloud environment at a time — a one-to-one relationship — so sandbox and production stay cleanly separated.

You can configure a dedicated Site ID in your Salesforce Commerce Cloud instance exclusively for Zest orders. Every order in that site is a Zest order — no additional filtering or custom attributes are needed for reporting or downstream workflows.

Zest can pass custom order attributes (such as the Zest order number and order type) to help you distinguish Concierge orders from other order sources in your reporting.

Zest polls Salesforce Commerce Cloud for order updates rather than receiving webhooks. For most gifting volumes this is seamless, but for high-volume campaigns with 1,000+ orders, allow up to approximately 15 minutes for all orders to sync.

Each Zest environment maps one-to-one with a Salesforce Commerce Cloud environment. To switch from a development to staging environment, update the Instance ID and Organization ID while keeping the same API credentials.

Zest connects to Commerce 7 via credentials set up during onboarding. Your Zest success manager handles all data formatting and field mapping to match Commerce 7's requirements — no technical configuration is needed on your end.

When a Concierge order includes multiple recipients, Zest automatically injects individual Child Orders into Commerce 7 — one per shipping address — with the gifter as the customer on each. These orders flow through your existing downstream integrations (ERP, warehouse, ShipCompliant, and others) without any additional setup.

Each order receives a note containing the Zest order number and invite number for easy reconciliation.

Setting up two separate Zest environments is strongly recommended before going live.

Tip for BigCommerce: Create separate API credentials in BigCommerce for sandbox and production to keep environments cleanly isolated.

Tip for Salesforce Commerce Cloud: Each Zest environment connects one-to-one with an SFCC environment. Use the same API credentials across environments and only swap the Instance ID and Organization ID in the URL when transitioning between dev, staging, and production.

If you're moving your ecommerce platform to Shopify while already using Zest, there's no need to rush the migration — and no additional Zest migration fees apply.

Expected downtime during cutover: approximately 1–2 hours.

Your existing Zest instance — including all historical orders, gift links, and collateral — is preserved. The switchover date does not need to coincide with your Shopify store go-live date; you can plan them independently.

If the API connection drops or an order fails to push, Zest retries automatically at increasing intervals. Most temporary issues resolve themselves without manual action. If orders remain stuck after the underlying issue is resolved, contact your success manager — they can review and unblock specific orders.

No. Zest operates entirely in the background and is not in the path of your website or checkout. Order and product data are synced asynchronously. Zest doesn't use a static IP address, so no firewall changes are needed on your side.