Supplier connections and price updates

Overview

• Connected supplier workflows keep Store supplier products and price history separate from the Ingredient master data.
• The Costing Dashboard treats failed connection tests, sync errors, and stale scheduled syncs as operational issues.
• A successful supplier price update can create Supplier Product Price History.
• Price-history entries that may affect linked Ingredients/Recipes are processed into Product Cost Reviews so the business can see the downstream margin impact.
• A sync does not automatically change the menu selling price or silently mark a Cost Review as accepted.

When to use this

• Use supplier sync/update whenever connected supplier catalogue pricing should be refreshed, and review the resulting Cost Reviews afterward.

Step-by-step

1. Open the selected Store's Supplier.
2. Test the connection when configuring or diagnosing credentials.
3. Run the supported update/sync.
4. Check Last updated and any sync error.
5. Open Cost Reviews for downstream product-cost changes.
6. If the Dashboard shows queued price histories, process/reprocess them before assuming impact reviews are complete.

Common mistakes

• Do not interpret 'catalogue updated' as 'all products are matched to Ingredients'.
• Do not manually edit selling prices simply because a supplier sync completed; review the actual Product cost impact first.
• Do not ignore stale/failed sync warnings if current supplier cost matters to pricing decisions.

Troubleshooting

• If a new supplier price does not appear in Product cost, check Store, currency, effective price, Ingredient mapping, active purchase option, and queued Cost Review processing.
• If sync repeatedly fails, resolve the supplier connection rather than overwriting the derived cost path.