Shopify batch fulfilment: what happens to 250 WhatsApp shipping messages

Shopify now fulfils up to 250 orders in one batch. How Beacon Messenger turns that burst of fulfilment webhooks into shipping messages, in what order, and what to check first.

On 16 October 2026 Shopify added batch fulfilment to the Orders page. Select the orders, click Create batch, and up to 250 fulfilments move through a pick, print and pack workflow together: one pick list, labels bought in one go, packing slips and customs forms printed as a stack, then scan to verify each item. For a store that used to fulfil order by order, Monday morning just changed shape. Two hundred orders that took the morning now go out before the coffee is cold.

Which raises a question that nobody asks until the first batch ships: what does the WhatsApp side do when 200 fulfilments land in a few minutes instead of spread across a morning? This post follows the batch through Beacon Messenger step by step, from the webhooks Shopify sends to the order the messages leave in, and ends with the three settings to check before you run the first one.

A batch is still 250 separate fulfilments

The first thing to know is that Shopify did not invent a new object. A batch is a workflow around ordinary fulfilments, and when the Print step buys labels, each order gets its own fulfilment with its own tracking number, exactly as if you had clicked Fulfil item on each one. Shopify then sends a fulfillments/create webhook per fulfilment, and a fulfillments/update webhook when tracking is added or changed.

Beacon Messenger subscribes to both topics. So a 250 order batch produces at least 250 create webhooks and usually a matching set of updates, arriving over the few minutes it takes Shopify to buy the labels. Nothing about them says batch. The app treats each exactly as it treats a single fulfilment, which is the point: the rules below are the same ones described in the post on split shipments and tracking added later, applied 250 times.

What each webhook has to pass

  1. The fulfilment status must be success. Shopify sends webhooks for pending and cancelled fulfilments too; those are dropped on arrival.
  2. The Shipping update automation must be enabled for the store. If it is off, every webhook in the batch is ignored and nothing is logged.
  3. The fulfilment must not already have a message. Each fulfilment gets a key made from the store, the trigger and the fulfilment ID, and if a message with that key exists and was not skipped, the webhook is dropped. This is what stops the create and the update for the same fulfilment producing two messages.
  4. If the fulfilment has no tracking number yet, the template decides. A template that uses tracking fields (tracking number, carrier, tracking URL) waits for the update webhook that carries them. A template with no tracking fields sends on create, because it has everything it needs. An update without tracking never sends.

In a batch the tracking question mostly answers itself. Labels are bought inside the batch, so by the time the fulfilment is created it normally has its tracking number, and the create webhook passes the fourth check on its own. If your batch uses a step that fulfils first and adds tracking later, the create is held and the update sends, which is the same behaviour as a manual fulfilment with tracking pasted in afterwards.

The queue, and why the messages do not all leave at once

A webhook that passes the checks does not send a WhatsApp message directly. The app fetches the order (customer name, phone, items, order status URL), builds the message context and puts a row in a queue, then asks the queue to run shortly. The handler returns to Shopify in well under its timeout, which matters when 250 of them arrive together; a handler that called WhatsApp inline would start timing out and Shopify would start retrying, doubling the load.

The queue runner takes the 25 oldest due rows, locks them so a second server process cannot pick the same ones, and sends them one after another. A webhook burst kicks the runner about a quarter of a second after the first row lands, and a scheduler also sweeps the queue every 30 seconds regardless. So a batch of 250 does not go out as 250 simultaneous calls to WhatsApp; it drains in groups of 25, oldest first, and the whole batch is typically out within a few minutes of the last label being bought. Customers receive their message in roughly the order their labels were printed.

If WhatsApp rejects a send with a transient error, the row is released and retried later with a growing delay (two minutes, then four, capped at fifteen), up to three attempts. A permanent failure, such as a number that is not on WhatsApp, is recorded as failed and does not retry. Both show up in the message log with the reason, which is where to look if a batch produced fewer messages than orders.

Three numbers to check before the first batch

Limits a 250 order batch can meet
LimitWhere it comes fromWhat happens at the limit
Monthly messages: 50, 500, 2,500 or 10,000Beacon Messenger planEvery further event this month is skipped with the reason Monthly limit reached; nothing is sent partially
Unique customers per 24 hours: 250 on a new number, rising to 1,000 and beyondWhatsApp messaging tierWhatsApp rejects the extra sends; they appear as failed and retry as above
Fulfilment webhooks per batch: up to 250Shopify batch sizeNone; this is the ceiling the other two are measured against

The monthly cap is the one that catches stores on the Starter plan. A single 250 order batch on a 500 message plan uses half the month in one morning, and the order confirmations for those same orders already used some of it. The dashboard post explains how the counter works and why a failed message still counts. If batches are going to be your normal Monday, size the plan to the month, not to the day.

The WhatsApp tier is the one that catches new numbers. A business number that has not built up its tier can start 250 conversations with unique customers in a rolling 24 hours. A 250 order batch to 250 different customers lands exactly on that line, and if the order confirmations earlier in the day already opened conversations with some of them, those do not count twice, but any new ones over the line fail. The post on the 250 message limit covers how the tier rises and how to tell a tier failure from a bad number.

What to look at after the batch

  • The message log, filtered to shipping update and today. The count should match the number of fulfilments with a phone number on the order. Skipped rows name their reason: no phone, no consent where required, limit reached.
  • Any failed rows. A cluster of failures with the same error at the same minute is a tier limit. Scattered failures are bad numbers.
  • One delivered message, opened on a phone. Batch tracking numbers are real tracking numbers, and the Track order button should resolve to the carrier page for that parcel.

Nothing to configure, one thing to decide

There is no batch setting in Beacon Messenger because there is nothing batch specific to set. The automation, the template and the dedupe rules you already have carry over. The one decision is the template itself: a template with tracking fields waits for tracking, which in a batch is almost always present at creation; a template without them sends the moment the fulfilment exists. If you print labels outside Shopify and add tracking later, keep the tracking fields so the message waits. If labels come from the batch, either works, and the one with tracking is the one customers prefer.

Questions about batch fulfilment and WhatsApp

Will a customer with two orders in the same batch get two messages?

Yes, one per fulfilment, because each order is fulfilled separately inside the batch and each has its own tracking number. The messages are a few seconds apart and each names its own order. A customer with two fulfilments on one order (a split shipment) also gets two, as the split shipments post explains.

Why did a 200 order batch produce 180 shipping messages?

Open the message log and filter to skipped. The usual gap is orders with no phone number or with a number that could not be normalised to international format. If the missing ones are failed rather than skipped and share a timestamp, you hit the WhatsApp messaging tier for your number.

Can the batch send the shipping message before the label is printed?

Only if your template uses no tracking fields, in which case the message goes out when the fulfilment is created. With tracking fields in the template the app waits for the webhook that carries the tracking number, which in a batch is normally the create webhook itself since labels are bought inside the batch.

Does the app slow the batch down or hold up Shopify?

No. The webhook handler queues the message and returns immediately; the sending happens afterwards in groups of 25. Shopify finishes buying labels at its own pace and the messages follow within minutes.

More guides