Reference · built on requestOperator by FibricSales, quotes & revenue

Price List Drift

Compares storefront and quote prices with the ERP price list and proposes a correction for every item that no longer matches.

About

Price List Drift treats the ERP as the price of record. It reads each item's unitPrice and lastModifiedDateTime from Business Central, then reads the same items where prices are copied: Shopify ProductVariant price and compareAtPrice, BigCommerce price list records, Salesforce PricebookEntry UnitPrice, HubSpot line items on open quotes, and Pipedrive product prices.

Where a copy differs from the record, it proposes the correction with both values, the item key used to match, and when the ERP price last changed. A pricing owner approves per item or per batch. Storefront and CRM prices change only after that approval, and the previous value is kept.

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

  • ERP price of record: Business Central items with number, gtin, unitPrice, priceIncludesTax, and lastModifiedDateTime
  • Storefront prices: Shopify ProductVariant sku, price, compareAtPrice, and updatedAt under read_products
  • BigCommerce price list records with variant_id or sku, price, sale_price, currency, and bulk_pricing_tiers
  • CRM price books: Salesforce PricebookEntry with UnitPrice, UseStandardPrice, IsActive, and ProductCode
  • Open quotes: HubSpot line items with hs_sku, price, and hs_discount_percentage on quotes in DRAFT or PENDING_APPROVAL; Pipedrive products with prices by currency

Proposed actions

  • Target capability: propose a Shopify variant price change through productVariantsBulkUpdate with the old and new price shown per variant
  • Target capability: propose a BigCommerce price list record upsert through POST /v3/pricelists/records for the mismatched sku and currency
  • Target capability: propose a Salesforce PricebookEntry UnitPrice update, or a Pipedrive product price change through PATCH /api/v2/products/{id}
  • Target capability: propose a line correction on an open HubSpot quote through PATCH /crm/v3/objects/line_items/{lineItemId}, before the quote is published

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

What you can build

  • Business Central to Shopify

    Read unitPrice per item, match Shopify variants by sku, and propose productVariantsBulkUpdate for each variant whose price differs, with allowPartialUpdates left off.

    With Microsoft Dynamics 365 Business Central, Shopify

  • BigCommerce price lists per customer group

    Compare each price list record's price and currency with the ERP list and propose the record upsert, respecting the batch size of 100.

    With BigCommerce, Microsoft Dynamics 365 Business Central

  • Salesforce price book audit

    Match PricebookEntry ProductCode to the ERP item number and propose UnitPrice updates where UseStandardPrice is false and the value has drifted.

    With Salesforce Sales Cloud, NetSuite

  • Open HubSpot quotes

    Before a quote reaches APPROVED, check each line item's price against the ERP and propose the fix on the line, with the rep notified in Slack.

    With HubSpot, Slack

Requirements

  • An ERP that holds the price list by item: Business Central items, or NetSuite items through REST record and SuiteQL
  • A shared item key across systems: sku, gtin, or ProductCode
  • At least one downstream price copy: Shopify, BigCommerce, Salesforce price books, HubSpot quotes, or Pipedrive products
  • A pricing owner who approves corrections and a rule for tax-inclusive prices
Authentication
An ERP API user with item read, a store token with read_products and write_products or the BigCommerce price list scopes, and a CRM token with product and line item write scopes.

Limits

  • It compares one item key. Items with no sku or gtin in one of the systems are listed as unmatched, not corrected.
  • Tax handling follows the ERP's priceIncludesTax flag. A storefront that shows tax-inclusive prices needs the rule set before the first run.
  • Published quotes are read only. A quote already sent to a customer is never repriced.
  • It does not set promotional prices. A compareAtPrice or sale_price is reported, never invented.

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 Price List Drift ↗

Questions and answers

What does the pricing owner approve?
A list of items, each with the ERP price, the copy's price, the key that matched them, and the date the ERP price last changed. Approval can be per item or for the whole batch. Rejected items are recorded and not proposed again until the ERP price changes.
Which direction do corrections flow?
From the ERP outward. It never writes to the ERP item. If the ERP itself is wrong, the proposal is a note for the pricing owner, not a change.
What record is left after a correction?
Item key, each system read, the two prices, the proposal, the decision, who made it, and when. The previous price is stored with each change so it can be put back with one approval.
Ask about Price List Drift

Ask about the capabilities and requirements in this listing.

For project-specific requirements, contact Fibric.