Quick answer
- The Excel import is in a test phase. Until it opens to every supplier, its card shows Coming next, and the steps below describe it as it will work.
- In Vinius, open Catalogue, go to Integrations and choose Connect on the Excel import card.
- Click Download the template. It comes in the language you use Vinius in, and Vinius reads it back in any of its seven languages.
- Fill in one row per product. Your own product code goes in every row: it is how the next upload finds the product again.
- Choose Upload and check. The first upload is the integrity check, so nothing reaches buyers yet.
- Do the spot check, then click Publish the catalogue. From then on, every upload is a sync.
When to use it
The Excel import suits every supplier, whatever system you work in. It is the way in when you have no Odoo webshop, and a quick first load when you do.
A file also works next to another integration. Your Odoo feed may carry your wines without trade prices, for example. A file with just your codes and prices then adds the prices to the wines the feed brought in. See A price list only below.
The template
The template has one sheet with a header row and two example rows. Each header carries a note that says what the column takes. Leave the examples in or delete them: Vinius skips them either way.
| Column | What goes in it |
|---|---|
| Code | Required. Your own product code, once per row |
| Type | Empty for a wine. Otherwise glassware, decanter or other |
| Producer | Required for a wine. The producer as on the label, without words such as "Champagne" or "Weingut" in front |
| Name | Required. The wine's name without producer, vintage or size, such as "Cuvée Prestige Brut". For an item, its name |
| Vintage | A year, or NV for a non-vintage wine |
| Bottle size | 75 cl, 0.75 l or 1500 ml. Empty means a 75 cl bottle. A case, written 6 x 75 cl, is set aside until packs can be published |
| Style | Red, white, rosé, sparkling, dessert, fortified or orange |
| Country | The country's name, or its three-letter code (FRA) |
| Region | Optional. The region or appellation |
| Classification | Optional. Grand Cru, 1er Cru, DOCG and the like |
| EAN | Optional. The barcode. It helps link the wine to one Vinius already knows |
| Price excl. VAT | Optional. Your trade price per bottle or piece |
| Currency | Optional. EUR when empty |
| Availability | Empty for available. Otherwise limited, out of stock or discontinued |
| Image link | Optional. A link to a bottle photo. Vinius reviews it before any buyer sees it |
You can keep your own columns next to these, such as a stock location or a margin. Vinius ignores every column it does not know. The header row may sit below a title row, as long as it is within the first ten rows.
Prices in the file are always trade prices excluding VAT. Nothing else is asked about them.
Steps
- Open Catalogue, go to Integrations and click Connect on the Excel import card.
- Click Download the template and fill it in. Save it as an Excel workbook (.xlsx).
- Under What the file holds, choose The whole catalogue.
- Click Upload and check. Vinius reads the file the way a sync would and writes nothing.
- Read the report. When a check fails or products are left out, fix them in the file and upload it again.
- Do the Spot check: mark each wine in the sample Right or Wrong, then click Confirm spot check. One wrong wine sends you back to step 5.
- Once the integration shows Ready, click Publish the catalogue. The checked file is applied straight away.
There is no schedule. Your next upload is your next sync.
Uploading again
Upload a new version whenever your catalogue changes. Choose what the file holds first:
- The whole catalogue. Products missing from the file become unavailable for buyers. Vinius deletes nothing, so a product that returns in a later file is listed again.
- Only some products. Vinius changes the products the file names and leaves the rest as they are.
Every upload runs the same checks as the first. An upload that changes much more than usual is held before anything is published. You then choose Apply anyway or Discard. How the checks and guards work.
A file has at most 5,000 rows. A larger catalogue goes up in parts, each uploaded with Only some products.
A price list only
A row whose code Vinius already links to a wine needs nothing but the code and what changed. The wine fills in the rest: producer, name, vintage and bottle size. An empty availability keeps the availability the product has.
So a file with two columns, Code and Price excl. VAT, updates the prices of the wines your codes already name. Upload it with Only some products, so nothing else changes.
A code Vinius does not know yet still needs its producer and name. Without them, the row is left out.
When the upload is refused
| Message | What to do |
|---|---|
| This is not an Excel file | Save the file as an Excel workbook (.xlsx) and upload it again. CSV and older .xls files are not read |
| No header row with the template's column names | Start from the Vinius template, or rename your headers to match it |
| The file has no product code column | Add the Code column. Every row needs your own code |
| The file has no product rows | Fill in at least one row below the header |
| More rows than one upload can hold | Split the file and upload the parts with Only some products |
| The file is too large | Remove images and other sheets, then upload it again |