Skip to content
Ordermatic Docs

Per-Customer Pricing Authority Signoff Plan (Genfit, CK, VMS)

Status: APPROVED Last Updated: June 1, 2026 Ticket ID: ENG-276 Related Plans: pricing-regression plan (Acceptance #7, PR-1, UC-2), docs/runbooks/ck-pricing-prod-rollout.md

1. Executive Summary

Section titled “1. Executive Summary”

In accordance with the main rollout plan and CEO review premises (PR-1, PR-2, and UC-2), the rollout of the per-customer pricing authority policy (gated under the P13 feature flag) is strictly dependent on capturing explicit signoff from each customer’s account owner. This policy defines whether the ERP/WhereFour pricing tiers are canonical or if operator-driven/PO-based manual overrides are allowed.

This document serves as the formal register of the captured signoffs for Genfit (P21), Cleveland Kitchen (WhereFour), and VMS (Enterprise MIS / POC). Additionally, any known exception cases where the purchase order (PO) pricing should override the canonical ERP/WhereFour tiers are documented in detail below to guide the validator’s behavior during flag flip.

2. Customer Signoffs Register

Section titled “2. Customer Signoffs Register”

All three required signoffs have been successfully captured and verified. Below are the details, contacts, and communication threads.

2.1 Genfit (Prophet21)

Section titled “2.1 Genfit (Prophet21)”
  • Goal: Confirm that erp_effective_prices rows (materialized from P21) and WhereFour price_tier_ids are the canonical sources of truth for pricing.
  • Account Owner Contact: David Boone (ERP Unlocked)
  • Advisor & Genfit-Side Contact: N3 (Genfit-side advisor)
  • Signoff Confirmation: Confirmed that for Prophet21/Genfit customers, the effective prices derived from P21 and WhereFour pricing tiers are 100% canonical. No customer-level PO overrides are permitted without explicit admin intervention.
  • Captured Signoff Link: Slack Thread - Genfit Pricing Policy Signoff

2.2 Cleveland Kitchen (WhereFour)

Section titled “2.2 Cleveland Kitchen (WhereFour)”
  • Goal: Confirm WhereFour tier pricing is canonical, except for specific, well-defined PO override cases (promos, spot quotes, freight-inclusive, and UOM mismatches).
  • Account Owner Contact: Dan-CK
  • Signoff Confirmation: Confirmed that the WhereFour tier pricing rules are canonical under normal conditions. However, the system must support overrides for documented edge cases.
  • Captured Signoff Link: Coda Thread - Cleveland Kitchen Pricing Authority

2.3 Visual Marking Systems (VMS - Enterprise MIS / POC)

Section titled “2.3 Visual Marking Systems (VMS - Enterprise MIS / POC)”
  • Goal: Confirm that the PriceComparisonCard provenance labels correctly represent the UX for extracted orders. (Note: VMS is extraction-only, with no submit path).
  • Account Owner Contact: VMS Team / Account Owner
  • Signoff Confirmation: Confirmed that the provenance labels displayed on the PriceComparisonCard are correct and appropriate for the extracted orders during the POC review.
  • Captured Signoff Link: Email Thread - VMS Provenance Label Approval

3. PO-may-be-canonical exceptions

Section titled “3. PO-may-be-canonical exceptions”

For certain customers, the pricing specified on the incoming Purchase Order (PO) takes precedence over the standard ERP or WhereFour pricing tiers. During the P13 flag flip, these exceptions are honored.

Below are the documented exceptions for each customer:

3.1 Cleveland Kitchen (CK) PO-may-be-canonical exceptions

Section titled “3.1 Cleveland Kitchen (CK) PO-may-be-canonical exceptions”

For Cleveland Kitchen, WhereFour tier pricing is canonical unless one of the following exception criteria is met, in which case the incoming PO price must be treated as authoritative:

  1. Promotional Pricing (Promos):

    • Rule: If a temporary promotion is active for a customer that is not yet configured in WhereFour’s pricing tiers, the PO price takes precedence.
    • Handling: If overrideUnitPrice = true is set by the operator, the validator preserves the PO/operator price override.

  2. Spot Quotes / One-off Deals:

    • Rule: If a specific shipment or transaction is subject to a spot quote negotiated between the sales team and the customer, the PO price is canonical.
    • Handling: Operator manually validates and flags the line item to bypass tier defaults.

  3. Freight-Inclusive Pricing:

    • Rule: Some customers negotiate POs where freight costs are baked into the unit price of the items (rather than listed as a separate shipping line item). This temporarily inflates the unit price relative to the WhereFour tier price.
    • Handling: Recognized via discrepancy alerts; operator overrides the default tier pricing to accept the freight-inclusive PO price.

  4. UOM (Unit of Measure) Mismatches:

    • Rule: When the PO orders in a different unit of measure (e.g., cases vs. individual units) than what is defined in the WhereFour customer tier, the price will appear to be mismatched.
    • Handling: The system flags the mismatch, and the operator-driven translation overrides the automatic WhereFour tier computation to prevent incorrect billing.

3.2 Genfit (P21) exceptions

Section titled “3.2 Genfit (P21) exceptions”
  • Rule: None. Prophet21 erp_effective_prices and WhereFour price_tier_ids are strictly canonical.
  • Handling: No operator-driven PO price overrides are permitted to bypass P21/WhereFour pricing authority.

3.3 VMS exceptions

Section titled “3.3 VMS exceptions”
  • Rule: None. VMS is extraction-only, with no submit path. The PriceComparisonCard correctly shows provenance labels to the user, and no automated pricing overrides are submitted back to Enterprise MIS.

4. Policy Implementation & Feature Gating

Section titled “4. Policy Implementation & Feature Gating”
  1. P13 Feature Flag Flip (Per-Customer Pricing Authority):
    • Gated on the pricingConfig.preferTierOverOverride connection parameter.
    • When enabled, the system automatically omits unit-price overrides in submission payloads for lines where (a) a valid tier is matched and (b) the price is not explicitly overridden by an operator (overrideUnitPrice = true).
  2. Auto-Repricing Gate:
    • Governed by pricingConfig.autoRepriceOnExtraction.
    • For CK and Genfit, this allows the system to re-price items instantly at extraction time, matching the canonical source of truth signed off in this document.