Purchase Order Software for Wine and Spirits Shops
Rebridge reads a distributor invoice, works out what every line is against your own catalog, and builds a Lightspeed purchase order you approve line by line. It fits how you already keep wine: vintages rolled into the name, carried on an axis, or kept as separate items. Nothing is sent until you approve it.
What a wine and spirits document actually carries
This part is not about your catalog. It is about the paperwork your suppliers send, which anyone who receives it can check.
- Billed by the case, sold by the bottle
- A distributor line states cases and a case price, while the thing you sell and count is the bottle. The quantity that belongs on a purchase order is cases times the pack, and the cost is the net bottle cost after any discount on that line.
- Split cases and the fees that ride with them
- Part-cases are common and are often charged for. A split-case fee sits on the line rather than in the header, so it has to land in the unit cost rather than being dropped or spread across the whole document.
- The description carries everything
- Producer, cuvee, appellation, varietal, vintage and bottle size are packed into one string, in a different order by distributor, and abbreviated differently by each. Reading it is a parsing problem, not a lookup.
- Formats that are not sizes
- Half bottles, magnums, 375s, 187s, cans and four-packs change what the unit is, not just how big it is. A line that reads 6/1.5L is six magnums, and reading it as twelve 750s is a quantity error and a cost error at once.
- Distributor codes that only partly exist
- Many distributors print their own item number, in their own format, and your catalog may hold some of them already. Coverage is never complete, so a system that depends on codes alone will go quiet on everything else.
- Documents that are not invoices
- Bills of lading and pre-arrival paperwork arrive in the same pile and carry no prices. They look like invoices to anything that is only pattern matching.
How your catalog is built decides what happens next
There is no right way to keep a catalog in this trade, and Rebridge does not hold an opinion about yours. It reads the one you already have. How it learns that is the same for every trade.
| If your | Then a line on the document |
|---|---|
| catalog keeps one item per wine and size, and you rename it when the vintage turns | a new vintage is not a new product. The line matches the item you already stock, so you are reordering and updating one product rather than ending up with the 2023 and the 2024 side by side. The title change stays yours to make. |
| catalog carries the vintage as an axis on the label | the same line is a new value on that axis. It joins the label you already carry instead of creating a second one beside it, and the quantity lands against that value. |
| catalog keeps a separate item for every vintage | it is genuinely a new product, and it gets set up as one, in your categories and following the naming you already use. |
| catalog has no variants at all, with everything written into the item name | there is no variant grid to fill in, because your catalog has none. Every line is either something you stock, which is a reorder, or something you do not, which is a new product. |
| catalog separates bottle sizes into their own items | a 375 and a 750 of the same wine are two different products, and a line is matched to the one whose size it states rather than to whichever shares the name. |
Why it learns your catalog rather than your trade
- Software that picks one shape for a trade is wrong for everyone it did not guess. There is no shape worth picking here, so Rebridge does not pick one. It reads the catalog you already have and builds its understanding of your store from that.
- When you connect, it audits your catalog into a profile: how you name products, what your axes are and what you call them, how you handle sizes and formats, and the grammar of your own item numbers. That profile is yours. It is not a template for your trade with your name written on it.
- Your catalog is the authority, not the document. A word your own catalog knows is never treated as a supplier's formatting, which is what keeps a producer's name attached to the line it belongs to when a distributor repeats it down every row of the page.
- It keeps learning as your documents arrive: how each distributor abbreviates, how they print sizes and pack counts, and which of their item numbers point at which of your products. A distributor you buy from twice a year accumulates the same way as one you buy from weekly.
- Everything it works out is a proposal that waits for you, and once you have confirmed something it is not overwritten by a later pass. The knowledge it builds about your catalog is yours, and you are the one who signs it off.
Common questions
- How does Rebridge handle a new vintage?
- It depends on how your catalog is built, and Rebridge works out which one you are from the catalog itself rather than assuming. If you keep one item per wine and size and rename it when the year turns, the line matches the item you already have, so you are reordering one product rather than creating a second. If you carry vintage as an axis, it is a new value joining the label you stock. If you keep a separate item per vintage, it is a new product and gets set up as one. The engine reads your structure; it does not impose a convention on your catalog.
- The invoice is in cases and I sell bottles. What goes on the purchase order?
- Bottles, at the net bottle cost. Distributor lines state a case quantity and a case price, while the unit you stock, count and sell is the bottle. Rebridge converts the line into the unit your catalog actually uses, so the purchase order quantity is cases times the pack and the cost is what one bottle costs you after the discount on that line. Split-case fees belong in that unit cost rather than being dropped or smeared across the document.
- Can it read a scanned invoice rather than a PDF with text in it?
- Yes. Scans are read the same way as a PDF with text in it, and the harder part is not the scan, it is that producer, cuvee, appellation, varietal, vintage and size are packed into one description string, in a different order and with different abbreviations for every distributor. Rebridge takes the string apart and reasons about the pieces rather than treating it as an opaque code to look up.
- What happens when the distributor's item number is not in my catalog?
- It falls back rather than giving up. Distributor codes are useful where they exist and do not cover everything, so a system that relies on them alone goes silent on the rest of the document. Rebridge also reads the name, the size and the price against what that distributor has sold you before, and where two candidates are genuinely close it asks you rather than picking. A question you can answer in a second is better than a duplicate you find a year later.
- Does it know the difference between a 375, a 750 and a magnum?
- Yes, and it treats format as part of the identity rather than as a size on a slider. Half bottles, magnums, 187s, cans and four-packs change what the unit is. A line reading 6/1.5L is six magnums, and reading it as twelve 750s would be wrong about both the quantity and the cost. If your catalog keeps formats as separate items, a line is matched to the item whose format it states.
- What if the document is not an invoice at all?
- Bills of lading and pre-arrival paperwork arrive in the same pile and carry no prices, and anything doing pure pattern matching will happily turn them into products at zero cost. Rebridge shows you every line with what approving would do before anything is created, so a document that should not become a purchase order does not quietly become one.
Rebridge works with Lightspeed R-Series and X-Series. The homepage walkthrough runs a thirty-line document end to end, and every line waits for you before anything reaches Lightspeed.