Reference · built on requestOperator by FibricOrders & fulfillment

Backorder Notice

Tells a customer whose order is waiting on stock the new date and their choices, drafted from the inbound purchase order.

Request accessPricing ↗

About

An order that cannot ship because a line is out of stock usually sits silent until the customer writes in. This operator reads the fulfillment orders your store or warehouse has placed on hold for missing inventory, finds the open purchase order for that SKU and its expected receipt, and works out the earliest date the order can leave. It then drafts the notice: what is delayed, the new date, and the choices you allow, such as wait, ship the in-stock lines now, swap, or cancel.

You approve the notice before it goes out by email or text. When the purchase order date moves again, it proposes a second notice rather than sending one quietly. Each notice is recorded against the order with the purchase order it relied on.

This is a reference listing. It documents what Fibric would read from Backorder Notice and what it could propose, based on the vendor's published interfaces. Fibric builds it under a managed deployment when you request it; selecting it here installs nothing.

Inputs

  • Shopify fulfillment orders with a fulfillment hold whose reason is INVENTORY_OUT_OF_STOCK, and the line items on hold
  • ShipHero Order Backorder webhooks, and ShipBob order.shipment.exception events raised for out-of-stock items
  • Open purchase orders with po_date and quantity_received per line in ShipHero, or purchase orders and receipts in Katana
  • Open sales orders with promised ship dates from NetSuite saved searches, and item fulfillments as they post
  • The customer's email, phone, and preferred channel on the order
  • Bounces and suppressed addresses in Postmark, so a notice is not proposed to an address that cannot receive it

Proposed actions

  • Target capability: propose an email through Postmark, or a text through Twilio, naming the delayed line, the new date, and the options
  • Target capability: propose splitting the fulfillment order so the in-stock lines ship now, if the customer chooses that option
  • Target capability: propose releasing the fulfillment hold once the purchase order is received
  • Target capability: propose cancelling the held line and the refund request when the customer chooses not to wait
  • Target capability: propose a note on the order recording the notice sent and the purchase order date it quoted

Proposed actions are target capabilities. Every action runs propose-first and needs a validated deployment and the appropriate permissions.

What you can build

  • Notice from the ShipHero backorder

    When ShipHero raises Order Backorder, read the open purchase order for the SKU, compute the new ship date, and propose the Postmark email with the wait, split, or cancel options.

    With ShipHero, Postmark

  • Ship what is here, hold what is not

    For a Shopify fulfillment order held for stock, propose the split so in-stock lines leave today and the held line follows when the Katana purchase order is received.

    With Shopify, Katana Cloud Inventory

  • Text the date change

    When NetSuite's promised ship date slips on an open sales order, propose a Twilio text with the revised date and a reply keyword for cancel.

    With NetSuite, Twilio

Requirements

  • A store or warehouse connector that marks orders held for stock: Shopify, ShipHero, or ShipBob
  • A purchasing source with expected receipt dates: ShipHero purchase orders, Katana, or NetSuite
  • A messaging connector with a sending identity you control, such as Postmark or Twilio
  • A written policy on which options a customer may be offered and after how many days a notice is due
Authentication
Uses the store, warehouse, purchasing, and messaging credentials already granted to the connected listings; no additional account is created.

Limits

  • The new date is only as good as the purchase order's expected date. If the supplier has not given one, the notice says so
  • It offers only the options in your policy. It does not invent discounts or substitutions
  • A refund or cancellation it proposes still runs through the store's own refund flow after approval
  • Orders held for reasons other than stock, such as address or payment issues, are outside its scope

Access and pricing

Reference listing. Fibric builds the operator under a managed deployment when you request it. Your quote covers the build, capabilities, usage, and support.

Request Backorder Notice ↗

Questions and answers

What does a person approve?
The notice text, the channel, and the date it quotes. If the customer replies with a choice, the resulting split, release, or cancellation is a second proposal with its own approval. Nothing is sent or changed on the strength of the first approval alone.
Where does the new date come from?
From the open purchase order for the missing SKU: its expected receipt plus the handling time you set. The notice names that purchase order. If the date changes, the operator proposes a fresh notice rather than editing the old one.
What does it never do without approval?
It never sends a message, splits or cancels an order, releases a hold, or issues a refund. It does not contact a customer twice about the same purchase order date.
Ask about Backorder Notice

Ask about the capabilities and requirements in this listing.

For project-specific requirements, contact Fibric.

This operator is developed, published, and supported by Fibric. Third-party names and logos identify the systems an integration connects to; they are the property of their respective owners, who are not affiliated with Fibric and do not sponsor or endorse this listing. Trademark policy