Reference · built on requestOperator by FibricSales, quotes & revenue

Reorder Prompt

Learns each account's reorder interval from its order history and proposes a reminder when a repeat purchase is overdue.

Request accessPricing ↗

About

Accounts that buy the same items on a rhythm go quiet for reasons nobody notices until the quarter ends. Reorder Prompt reads each account's order history from the ERP or the store, groups orders by item, and works out the gap between purchases. When the gap since the last order runs past the learned interval, the account is overdue for that item.

It proposes a reminder as a mail draft or as an event in your messaging platform, or a call task for the rep when the overdue value is large. Accounts with too few orders to learn from are listed for a person instead. Consent is read before any message is proposed.

This is a reference listing. It documents what Fibric would read from Reorder Prompt 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

  • Posted invoices per customer from Business Central salesInvoices, with customerNumber, invoiceDate, status Open or Paid, and their salesInvoiceLines
  • Shopify customers with numberOfOrders, amountSpent, and lastOrder, and their orders read through the orders query filtered by customer_id and created_at
  • BigCommerce orders through GET /v2/orders filtered by customer_id and min_date_created, and new orders as store/order/created webhooks arrive
  • The gap between an account's orders for the same item number or SKU, so the interval is per item, not per account
  • Orders placed since the last invoice and still open, so no reminder is proposed while an order is in flight
  • Whether the account may be messaged, from the consent your store or messaging platform records on the profile

Proposed actions

  • Target capability: propose a reminder to the buyer as a Gmail or Microsoft Outlook draft listing the items due and the last order date
  • Target capability: propose a Klaviyo event on the profile through POST /api/events, with the item and days overdue as properties, to start your reorder flow
  • Target capability: propose a call task for a wholesale account through POST /crm/v3/objects/tasks when the overdue value is above the amount you set
  • Target capability: propose the interval itself for an account with few orders, for a person to confirm or set by hand before any reminder

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

What you can build

  • Prompt wholesale reorders from Business Central

    Read each customer's posted salesInvoices and their lines, learn the interval per item number, and propose an Outlook draft through POST /me/messages when an item runs overdue.

    With Microsoft Dynamics 365 Business Central, Microsoft Outlook

  • Start a reorder flow for Shopify customers

    Read orders by customer_id and created_at, learn the gap per SKU, and propose a Klaviyo event with the SKU and days overdue so your flow sends the reminder after approval.

    With Shopify, Klaviyo

  • Send a rep after a large overdue account

    When a BigCommerce customer's overdue items exceed the value you set, propose a HubSpot call task for the account owner with the items and last order date.

    With BigCommerce, HubSpot

  • Hold while an order is in flight

    Before proposing, read the customer's open orders through the orders query with status open, and skip the reminder when one exists, noting it on the entry.

    With Shopify

Requirements

  • An order history with dates and items per customer: Business Central salesInvoices, Shopify orders, or BigCommerce orders
  • A messaging path: Gmail, Microsoft Outlook, or Klaviyo, and a CRM for rep tasks
  • Consent records for the accounts you intend to message
  • A minimum number of past orders you set before an interval counts
Authentication
An ERP API user with invoice read access, store API access with order and customer read scopes, and a mail or messaging platform token with draft or event write scope.

Limits

  • Shopify's read_orders scope covers orders from the last 60 days. The history behind an interval needs read_all_orders.
  • An account with fewer orders than your minimum gets no interval and no reminder. It is listed for a person.
  • The interval is learned from order dates alone. A seasonal account shows as overdue in its off-season unless you mark it.
  • Reminders wait for a person. A Klaviyo event is recorded only after approval, and its unique_id blocks a repeat.

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 Reorder Prompt ↗

Questions and answers

How is the interval learned?
From the dates of past orders for the same item, per account. It takes the gaps between orders and the pattern they make. An account with fewer orders than your minimum gets no interval. An interval you set by hand is used instead of the learned one.
What does a person approve?
The reminder or the task. The draft shows the buyer, the items, the last order date, the days overdue, and the text. On approval the draft is saved, the event is recorded, or the task is opened. The operator sends nothing; the rep sends the draft.
What record is left?
One entry per prompt: the account, the item, the interval used and how it was learned, the last order date, the proposal, the decision, who made it, and when. A Klaviyo event's unique_id is kept on the entry.
Ask about Reorder Prompt

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