Any system that promises to run your whole business is describing a destination, not a first month. WineFlow's job is narrower, and it is worth being exact about: it owns the path from your catalogue to a sent offer, and from an accepted offer to an order, an invoice and a shipment. Everything on this page stays where it is.
None of this is a roadmap tease. These are the boundaries of the product as it stands today, and each one is something we have deliberately not built rather than something we forgot.
What WineFlow does take over on day one
The spreadsheets. The catalogue with its prices and discount tiers, the stock file, the offer file, and the retyping between them and whatever your accountant uses. That is the whole proposition, and it is enough work to be worth doing on its own.
What stays where it is
Your accounting system
WineFlow has no general ledger, no chart of accounts and no VAT return. An invoice record in WineFlow holds the number, the status, the total and a reference to the document created on FattureInCloud; the accounting itself, and the electronic invoice sent to the Italian SDI, happen there. On Professional and Enterprise the two are connected. On Starter and Business there is no accounting connection at all — the invoice is issued in your accounting system, from the proforma WineFlow prepared.
A price list agreed with one specific customer
This one deserves to be stated precisely, because it is easy to imply otherwise. Pricing in WineFlow lives on the wine: list price, four discount tiers, your purchase price, the markup and the resulting selling price, plus a market reference. There is no per-customer price list and no per-customer discount record. If you have a different agreed price for each customer, that agreement still lives outside WineFlow. What you get instead is the price and the margin in front of you at the moment you build the offer, and an offer line that keeps a snapshot of what the price was that day.
Lot traceability and excise duty
Stock is counted per wine, per location, with the reserved part kept separate from the sellable part. There is no lot number, no batch, no expiry date, and nothing that produces an excise register or an e-DAS. If you run a tax warehouse, or a recall has to be traceable down to a lot, that system stays and WineFlow does not touch it.
Chasing what customers owe you
WineFlow does not record what customers pay you: there is no payment entry, and an invoice's status follows its e-invoice through SDI, not the money. So it will not tell you which invoices are still open, it does not age a receivable, it does not send reminders and it does not reconcile a bank statement. Your accounting system keeps that job.
Warehouse execution
Shipments, with their carrier, tracking number and documents, are in WineFlow. Packing lists, pallets, bin-level picking paths, barcode scanning and handheld terminals are not. It knows how many bottles are where and how many of those are already promised; it does not direct the person walking the aisle.
A shop
WineFlow is B2B. Offers go to named customers you already have a relationship with. It does not host a storefront, it has no public catalogue and it does not take card payments from your customers. Nor does it connect to one: the Shopify, WooCommerce and PrestaShop connectors earlier versions listed were withdrawn, so a shop you already run stays separate.
Making the wine
No harvest, no fermentation, no tank management, no bottling runs. WineFlow starts at a finished bottle that exists in your catalogue with a price on it. If you are a producer as well as a seller, the cellar side of your business is not in here.
People, payroll and the rest of the back office
WineFlow has users, roles and an audit trail over what those users did. It has no employee records, no payroll, no expenses and no contract management.
Carriers and invoicing: where the boundaries are
No carrier connector is offered on any plan: a shipment's carrier and tracking number are typed in by hand, not booked with DHL, UPS, FedEx, BRT or GLS. And below Professional there is no FattureInCloud connection, so proformas are prepared in WineFlow and the invoice is issued in your accounting system; that one is not a missing feature — the code exists and the plan decides.
Which integration sits on which plan is set out on the integrations page.
Why we put this in writing
A migration does not fail on the feature you evaluated. It fails on the thing nobody mentioned. If one of the boundaries above is load-bearing for how you actually work, we would rather find that out on the first call — and sometimes the honest answer is that WineFlow is the wrong shape for your business, which is a much cheaper answer now than in month four.
The next two questions
What can actually be imported, who owns the data and how long it takes: migrating from Excel and your accounting system.
What is connected today, on which plan: the integrations page.