Tasking via Wix

If you run a frozen or chilled store on Wix, you can hand your orders to The Frozen Food Courier™ automatically — no manual re-keying, no CSV exports, no spreadsheets. Because Wix is not WooCommerce, there is no native TFFC plugin to install. Instead, Wix (like any non-WooCommerce cart) connects through our hosted Carrier API, powered by the Cibarix™ platform. This guide explains how it works today and the two practical ways to get your Wix store tasking us.

The short version

Your Wix store sends each paid order to our Carrier API as a shipment request. We authenticate the call with an issued API key, create a waybill, and then push signed delivery-status updates back to you — keyed to your own order reference — as the parcel is planned, scheduled, dispatched, en route and delivered. Two routes exist:

• Build it on the Carrier API — if you (or your developer) are comfortable with Wix Automations, Velo, or any backend that can make an HTTPS request.
• Let us run a managed feed — if you would rather not build anything. We arrange an order feed on your behalf and take care of the integration.

Why Wix goes through the Carrier API

WooCommerce stores get a native TFFC plugin that drops shipping and dispatch straight into the admin. Wix has no equivalent TFFC app — and we are honest about that. What Wix does have is a capable automation layer (native Automations, event webhooks, and Velo backend code) that can call an external service when an order is placed or paid. That external service is our Carrier API. So the integration path for Wix is the API itself, either built by you or operated by us as a managed feed.

How the Carrier API works

The Carrier API is a hosted, standards-based service. Everything runs over HTTPS with a merchant-specific credential.

1. Authenticate. You are issued an API key. Each request carries it as a Bearer token over HTTPS. No key means no call — your account is isolated from every other merchant.
2. Post the order. For each order you send a shipment_request with an HTTP POST to carrier/v1/shipment. The canonical endpoint, request/response reference and credentials are provided on enrolment.
3. Get a waybill. We validate the order, resolve the delivery address, and return a waybill — the tracking spine that threads every hop of the journey.
4. Receive signed status updates. As the shipment moves, we send signed webhooks back to you, each keyed to your order reference so you can match it to the Wix order without guesswork.

The full API reference — exact fields, payload shapes, signing details and your credentials — is available on request when you enrol. See the canonical page: TFFC Carrier API.

What order data we need

A shipment request carries the essentials for a cold-chain delivery. Wix already collects all of this at checkout — the integration simply maps it into the request:

• Merchant identity — your issued merchant code, so we know which store the order belongs to.
• Your order reference — the Wix order number. We echo this back on every status update.
• Recipient contact — first name, last name, phone (mobile, for SMS/WhatsApp notices) and email.
• Delivery address — street/address line, suburb or city, province, postal code and country.
• Action — whether this is a new/updated task or a cancellation.

The exact field names and structure are in the API reference supplied on request. We never ask you to publish credentials or embed secrets in client-side code.

Route 1 — Build it on the Carrier API

If you have a developer or are comfortable in Wix, you can wire the store to the API yourself:

1. Enrol and get credentials. Contact us to be issued your API key and merchant code, plus the full endpoint reference.
2. Choose your trigger. In Wix Automations (or Velo backend code), pick the event that should task us — we recommend “Order is paid” so only confirmed orders create a waybill.
3. Call the API. On that trigger, send the POST to carrier/v1/shipment with the Bearer key and the mapped order data. Keep the key server-side (Velo secrets), never in front-end code.
4. Handle the response. Store the returned waybill against the Wix order.
5. Receive status webhooks. Point a Velo backend endpoint at our signed status callbacks and update the order as it progresses.
6. Test, then go live. Verify a real order end-to-end before switching on.

Route 2 — A managed order feed

Prefer not to build anything? For merchants who would rather stay out of the code, we can arrange a managed order feed: we set up and operate the connection from your Wix store into the Carrier API on your behalf, so your orders flow to us and status updates flow back without you touching Automations or Velo. Tell us about your store and we will scope it.

Talk to us about a managed feed →

Getting delivery status back

However you connect, we keep you and your customer informed as the order moves through planned, scheduled, dispatched, en route, delivered (or failed). You can consume this two ways:

• Signed status webhooks — the API pushes each change back to your endpoint, signed and keyed to your order reference, so your systems update automatically.
• Email notifications — no technical setup; acceptance, scheduling, dispatch and delivery confirmations arrive by email.

Handy extras

• Scheduled deliveries — capture a preferred delivery date at checkout (a Wix date-picker field) and pass it in the request.
• Frozen-only triggering — use Wix Automation conditions so only orders containing cold-chain goods task us.
• Cancellations & changes — send the cancel/update action to keep the waybill in step with the order.

What changed — a note on older setups

Earlier versions of this guide described stitching Wix to us with ad-hoc webhooks, third-party automation bridges (such as Make or Zapier), bespoke JSON hand-offs to a partner, or manual CSV exports. Those approaches are now superseded. The Carrier API is the single, supported, secure path — one authenticated endpoint, a proper waybill, and signed status updates — and the managed feed covers anyone who would rather not build. If you are on an older arrangement, contact us and we will move you across.

On WooCommerce instead?

If your store runs on WooCommerce rather than Wix, you do not need the raw API — we publish native TFFC plugins that handle shipping and dispatch inside WordPress. See TFFC plugins.

Get started

Ready to task The Frozen Food Courier™ from your Wix store? Read the Carrier API overview, then get in touch to be issued your credentials or to set up a managed feed. Tell us your store URL, your typical order volume, and whether you want to build the integration or have us run it.

Related reading: Tasking via Shopify · Setting Up Frozen Food Shipping in E-Commerce · Real-time Delivery Tracking.