Importing vendor offers

A vendor sends a price list; you want those prices on your ingredients without retyping them. The offers import takes one row per price: this vendor sells this ingredient in this pack at this price. Committed rows become vendor offers on each ingredient’s card, feeding its price history. The shared upload-map-check flow is described in CSV imports.

Columns

Field	Required	What goes in it
Ingredient	Yes	Matched by name against your inventory
Vendor	Yes	Matched by name; an unknown name creates the vendor
Price	Yes	What the pack costs, in your base currency
Quantity	Yes	The pack size that price buys
Unit	No	The unit of the pack size, if it differs from the ingredient’s
Vendor SKU	No	The vendor’s own reference for the item
Lead time (days)	No	Days between ordering and delivery
Min order qty	No	The smallest quantity the vendor accepts

Matching by name

The ingredient must already exist; import your ingredients first if needed. A row whose ingredient name matches nothing in your inventory is flagged. Use Map to ingredient on the row to point it at the right record, then save and recheck.

Vendors are more forgiving. An existing vendor matches by name (capitalization does not matter). An unknown name creates the vendor when you import, exactly like the manual offer form. Importing a new supplier’s full price list therefore creates the vendor once and attaches every offer to it.

Price and pack size

Price and Quantity describe the pack together. Rio Chili Farm sells fresh habaneros in 5 kg crates at 42.00: price 42.00, quantity 5, unit kg. BatchDash works that out to 8.40 per kg. A pack quoted in another unit converts into the ingredient’s unit (a 25 lb sack for an ingredient kept in kg), so unit costs stay comparable across vendors.

One thing an offer does not do: move stock. It records a price. Goods that actually arrived go through imported deliveries or a purchase order.