A back-in-stock email can be accurate about the product and still disappoint the customer. The shoe is available, but not in the size they requested. The link opens the right product family, but the wrong color. The email says “reserved for you,” although no reservation exists.
Create the message in Migma around the exact item the customer requested. Then have the BigCommerce and sending-platform owners verify the inventory event, recipient eligibility, destination, and final template. Treat availability as a fact to check at the relevant moment, not a promise that lasts forever.
This guide is published by Migma. Its examples and review process are editorial suggestions, not a tested conversion benchmark. Official platform pages were checked on October 16, 2026.
Write the item identity before the headline
Start your Migma brief with a small identity record. Include the product name, relevant size or color, approved image, destination URL, and the owner who can confirm the request. Use your store's actual variant identifiers internally; the customer usually needs the readable option names.
For a hypothetical footwear store, the requested item might be “Canvas low-top, terracotta, size 39.” A generic “Your favorite shoes are back” headline hides information that matters to the purchase. Put the distinguishing details near the main action, and use an image that matches them.
Brevo's BigCommerce email marketing article, visibly dated August 29, 2026, includes back-in-stock messages among ecommerce workflows. This guide narrows that broad topic to one acceptance question: does the creative describe the exact item the customer asked about?
Give each availability statement an owner
Separate the creative approval from the stock decision. Migma helps prepare and review the email; it does not establish that your BigCommerce inventory event is current or that a product is reserved for a specific recipient.
Use a short handoff record like this proposed example:
| Review item | Evidence the owner should supply |
|---|---|
| Requested option | Approved test record showing the expected size and color |
| Available option | Inventory check for that same option under the configured workflow |
| Image and label | Product image and readable option names that match the request |
| Product destination | Test click that reaches the expected option or clearly explains selection |
| Availability promise | Wording supported by the actual store behavior |
Do not assume a provider connector covers every row. The Brevo listing in the BigCommerce marketplace establishes that a Brevo app is listed; it is not evidence of a native Migma connection or of your store's specific restock configuration. Verify the configured workflow with its owner.
Choose copy that matches the destination
Use a direct message when the destination has been tested for the requested option. For the hypothetical shoe example, an original draft could read:
Subject: Terracotta canvas low-tops are available again The terracotta canvas low-top in size 39 is available again. Open the product page to check current availability and complete your order. Availability can change before checkout. Button: Check size 39
Only use the exact size and color if the recipient record and destination support them. “Check size 39” is a poor label if the link opens an unrelated category or a product with no visible size selector.
When the destination requires the customer to choose an option, explain that honestly. A second original direction is:
Subject: The canvas low-top is back to browse The canvas low-top is available again in selected options. Open the product page and choose your size and color to see what is currently available. Button: View available options
That broader message still needs appropriate recipient selection. It should not replace a requested-variant alert when the requested option remains unavailable. Resolve that mismatch with the workflow owner before approving the email.
Remove urgency that the store cannot support
A restock is useful news without an invented countdown. Avoid “last chance,” “only two left,” and “held just for you” unless the responsible system and owner establish those exact facts. A marketing calendar is not stock evidence.
If availability changes between sending and opening, the landing page needs a useful next step. Agree with the store owner whether the customer can select another option, request a new alert, or return later. Do not promise an alternative that the page does not actually offer.
Keep the email's useful information in text. An image may load slowly or be hidden, and a customer should still understand which item the message concerns. Describe the product accurately in alt text where the editing surface supports it.
Review the final handoff in Migma and the sender
Provide the approved identity record and brand context to Migma. Review the subject direction, product label, image, button wording, and support link together. Run Email Preflight and resolve relevant findings before handoff.
Use a documented export route that fits your destination, then review the resulting template in the sending platform. Verify its own variables, audience rules, tracking, and links. Do not assume a placeholder in a creative draft automatically becomes a working store field.
Test the received message with approved test records for more than one option. Include a case where the requested option is unavailable, and ask the workflow owner to confirm the expected behavior. Record the actual result rather than marking every successful send as a correct restock alert.
Before launch, keep one compact acceptance note: requested item, stock decision owner, final template version, tested destination, and any unresolved mismatch. Use that evidence to approve the Migma creative and the operational send separately.
Frequently Asked Questions
Does a product restock mean every variant is available?
Do not assume that. Have the inventory owner verify the exact requested size, color, or other option and confirm the configured alert behavior.
Can Migma confirm BigCommerce inventory?
This guide uses Migma to prepare and review creative. The store and sending-platform owners must verify inventory events, recipient eligibility, variables, and destinations.
Can the email say an item is reserved?
Use reservation language only when the responsible system and owner confirm that a reservation actually exists for the recipient. A restock notification alone is not evidence.
What should a restock test include?
Test the received message against the requested option, matching image and labels, actual product destination, and expected behavior when that option is unavailable.