Reference · built on requestOperator by FibricSales, quotes & revenue

Promise Check

Checks delivery dates on outgoing quotes against stock and inbound purchase orders and proposes a corrected promise before the quote leaves.

About

Promise Check runs before a quote leaves. When a rep readies a quote, it reads each line's delivery date and compares it with what the inventory system reports: units on hand, units already committed to other orders, units expected on open purchase orders, and the arrival date on those orders.

Where the quoted date cannot be met, it proposes a corrected one and shows its working. The rep or a manager accepts the correction, overrides it with a reason, or rejects it. The quote stays held until someone decides. Stock is not reserved and no purchase order is placed.

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

  • Quotes about to go out: HubSpot quotes in hs_status DRAFT or PENDING_APPROVAL with their line items and hs_expiration_date
  • Business Central salesQuotes in status Draft, with each salesQuoteLine's itemId, quantity, locationId, and the quote's validUntilDate
  • Stock per variant and location from Katana: quantity_in_stock, quantity_committed, quantity_expected, and safety_stock_level
  • Open purchase orders with status NOT_RECEIVED or PARTIALLY_RECEIVED and their expected_arrival_date, per row
  • Sales orders whose ingredient_availability is EXPECTED or NOT_AVAILABLE, or whose production_status is BLOCKED, since they compete for the same stock
  • Units on hand per ERP item, and the deal's closedate in the CRM, so the check knows when the customer expects an answer

Proposed actions

  • Target capability: propose a corrected delivery date on a quote line, shown beside the rep's date with the stock and arrival figures behind it
  • Target capability: propose holding the quote in PENDING_APPROVAL or Draft until a person accepts or overrides the corrected date
  • Target capability: propose splitting a line: the quantity on hand now, the remainder on the purchase order's expected_arrival_date
  • Target capability: propose a note on the deal recording the dates compared, the figures used, and who decided
  • Target capability: propose a message to the quote owner in Slack or Teams with the old date, the new date, and the reason

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

What you can build

  • Hold a HubSpot quote stock cannot meet

    When a rep moves a quote to PENDING_APPROVAL, compare each line item with Katana quantity_in_stock less quantity_committed, and propose a corrected date taken from the matching purchase order's expected_arrival_date.

    With HubSpot, Katana Cloud Inventory

  • Check Business Central quotes before send

    For each Draft salesQuote, read the item's inventory and the open purchase orders behind it, propose the corrected date per line, and hold the send action until a person approves.

    With Microsoft Dynamics 365 Business Central

  • Split a line between on-hand and inbound

    Where part of a quantity is on hand in Cin7 Core and the balance is inbound, propose two dates on the Pipedrive deal instead of one the warehouse cannot keep.

    With Cin7 Core, Pipedrive

  • Tell the rep before the customer finds out

    Post the old date, the corrected date, and the reason to the quote owner in Slack so the conversation with the customer starts from the right promise.

    With Slack, HubSpot

Requirements

  • A CRM or ERP that holds quotes with line items and a status that can be held: HubSpot quotes or Business Central salesQuotes
  • An inventory system that reports committed and expected stock per location and open purchase orders with arrival dates, such as Katana, Cin7 Core, or Unleashed
  • Supplier lead times recorded somewhere it can read: expected_arrival_date on open purchase orders, or a lead-time field on the item
  • One person per quote with the authority to accept or override a corrected date
Authentication
A CRM OAuth app or private-app token with quote and deal scopes, an inventory API key with read access, and an ERP API user that can read items and hold quotes.

Limits

  • It checks a date. It does not reserve stock, move stock, or place a purchase order.
  • A correction is only as good as the purchase order's arrival date. If a supplier never updates it, the proposal still shows the date used.
  • An item with no stock record and no open purchase order returns no basis for a date rather than a guess.
  • Quotes already sent are out of scope. The check runs while the quote is still held.

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 Promise Check ↗

Questions and answers

What does the rep or manager approve?
The corrected date. The proposal shows the date on the quote, the date computed, and the evidence: units on hand, units committed, units expected, and the purchase order arrival date used. The rep or their manager accepts it, overrides it with a reason, or rejects it.
Where do supplier lead times come from?
From the expected arrival dates on open purchase orders and from any lead-time field on the item in your inventory system. It reads what is recorded. It never contacts a supplier and never edits a purchase order.
What record is left after a check?
One entry per checked quote: quote id, each line's quoted and corrected dates, the stock and purchase order figures at check time, the decision, who made it, and when. If a date was changed, the entry names the original so it can be restored.
Ask about Promise Check

Ask about the capabilities and requirements in this listing.

For project-specific requirements, contact Fibric.