A Toast restaurant should compare its existing purchasing and inventory setup with the supplier work it still handles manually. Toast has back-office capabilities: xtraCHEF documentation includes vendors, ordering, inventory and recipe-cost workflows. A separate Toast Retail workflow supports purchase orders and receiving. These are distinct products and configurations, not evidence that every Toast account has the same features.
LineNow is an option when the remaining problem is supplier-order coordination: changed confirmations, substitutions, delivery timing, physical receiving or the handoff to accounting.
Begin with the restaurant's actual buying cycle
Take a recurring order from a produce vendor, broadliner or specialty supplier. List the steps your current setup performs and the work a person does outside it:
- Translate menu sales and recipes into a purchasing requirement.
- Validate counts, waste, yield, packs and already-open orders.
- Send through the supplier's accepted channel.
- Review confirmations, shortages, substitutions and prices.
- Receive actual goods and record rejected quantities.
- Resolve invoice differences and prepare accounting evidence.
If xtraCHEF or another connected tool already handles those steps adequately, adding software may not improve the operation. Evaluate the missing handoff rather than buying the same feature twice.
Understand the Toast connection
LineNow's Toast connection uses a read-only Standard API path. Treat it as a source for supported restaurant data; do not assume LineNow writes stock adjustments, recipes or supplier POs back into Toast. Verify access requirements, restaurant locations, data availability and freshness during setup. Toast's API requirements describe the access framework.
Menu sales are an ingredient-usage estimate only after recipe and unit mappings are correct. Waste, portion variation, staff meals and receipts still need physical or operational records. A POS connection does not remove stock counts.
If you are migrating to Toast, a pilot can start with manual POs and validated supplier items. Add the supported sales source when ready; do not treat an incomplete item import as ready for unattended replenishment.
Before a LineNow pilot, follow the Toast connection steps and recipe setup guide. Check access, restaurant mappings and ingredient units with the person who will maintain them.
Keep supplier changes reviewable
In LineNow, supported supplier messages can update the living PO with source context. The buyer decides whether to accept a changed price or substitute. A substitution can change allergens, usable yield, menu identity and cost—not just the item name.
For example, if a supplier confirms six cases instead of eight, expected incoming stock becomes six after review. If five usable cases arrive and one is rejected for condition, the receiver records five accepted and the rejection. Record whether the rejected case will be replaced or credited. The two cases the supplier never confirmed are a separate buying gap, not an accepted delivery balance. The invoice or supplier email is not proof that six usable cases arrived.
Email, WhatsApp Business, EDI and portal work require confirmation of the particular supplier route and supported setup. Personal texts or a website login are not automatically ingested.
Use planning with its limits visible
Replenishment can combine mapped usage, stock, lead time, order cadence, packs and safety stock. Compare the suggestion with actual demand and shelf life. Statistical decay is an operating assumption; it does not establish food safety, expiry, storage temperature or permission to sell a lot.
Recipe cost is also a model. Verify whether a changed purchase cost affects future recipe estimates, the received inventory valuation or a posted accounting period. Finance owns that distinction.
Reconcile open commitments and actual payment terms with finance before using purchasing records in a cash plan. Sales revenue is not bank cash.
Prove a complete supplier cycle
Choose one system to send the real order, one to record the physical receipt and one to post the bill. Test a changed confirmation, partial receipt, credit and failed handoff. Agree who follows up on an unconfirmed balance.
The ERP handoff is separate from the read-only Toast connection.
Measure buyer time, receiving corrections and unresolved invoice age on comparable orders. Confirm current pricing and trial scope, including the capabilities included in the quotation. Expand only after the restaurant can operate the workflow and recover exceptions reliably.