The integrity check, check by check

Quick answer

• The integrity check reads your catalogue exactly as a sync would, and writes nothing.
• Six checks judge the catalogue as a whole. All six must pass before you can schedule the sync.
• Findings judge single products. A finding leaves a wine out, sets a product aside as not wine, or publishes the wine with a warning.
• Fix at the source, in Odoo, then click Run integrity check again.
• Every scheduled sync runs the same checks, plus four guards against sudden large changes.

Reading the report

The report opens with Integrity check passed or Integrity check not passed, the counts and the six checks. Below it come the spot check, once the checks pass, and the findings. Each finding is a filter: click it to list the products it concerns, with their SKU, the name In the feed, what Vinius Read as, and the Result.

Left-out findings come first, largest at the top. Start there: they decide whether 90% of your wines are complete.

The six checks

All six must pass. A failed check blocks the schedule, however good the rest of the report looks.

The feed could be read

Vinius opened the link and found a product feed in it. When it cannot, there is no report. You see one of these messages instead:

To paste a new link into an integration that is already scheduled, click Pause, then Edit.

The feed has products

The feed holds at least one product. An empty feed stops the check with "The feed has no products." In Odoo, check that your wines are published on the webshop and that the Vinius feed has its categories chosen.

At most 5,000 products

One feed holds 5,000 products at most. A larger feed stops the check with "The feed has more than 5,000 products." First make sure the Vinius feed has the wine categories only. If your wine list alone is larger than that, contact Vinius before you split it.

Every SKU appears once

Vinius keeps track of each product by its code. When two products share a code, both are left out (SKU appears twice) and this check fails. In Odoo, give every product variant its own Internal Reference.

At least half of the products are wine

This check fails when more than half of the feed is set aside as not wine. That almost always means the feed has the wrong categories. In Odoo, open Manage feeds, edit the Vinius feed and keep the wine categories only.

At least 90% of the wines are complete

Of the products that are wine, at least 90% must be free of the findings that leave a wine out. The report shows your share next to the check. Work through the left-out findings below, the largest first.

The spot check

Counts cannot catch a reading that is wrong in the same way every time: the producer taken for the wine's name, a cuvée number read as the vintage, a magnum read as 75 cl. The spot check can.

Once the six checks pass, Vinius shows ten random wines from the ones it would publish. Each shows the name in the feed, how Vinius read it (producer, wine, vintage, bottle size and, when you declared one, the price) and the wine it matched in the Vinius catalogue, or that it is new. Mark each Right or Wrong, then click Confirm spot check.

One Wrong blocks the schedule. Fix the names in Odoo or the integration's settings, run the check again and do a new spot check.

Findings that leave a wine out

A wine with one of these findings is not published. The rest of your catalogue can still go live, as long as 90% of your wines are complete.

No SKU

The product has no product code in the feed, so Vinius cannot keep track of it from one sync to the next. Fill in the Internal Reference of the product variant in Odoo.

No name

The product has no name, or Vinius found no wine name in it. Give the product its full name in Odoo: producer, wine, appellation, vintage.

No producer

Vinius could not tell who made the wine. Put the producer in the product name, ideally first, or add a variant attribute named Producer.

Vintage unclear

Vinius found no year, and nothing that says the wine is non-vintage. Add the year to the product name, or as a variant attribute named Vintage. For a non-vintage wine, write NV or non-vintage in the name.

When every wine in your feed without a year is non-vintage, you can instead turn on A wine without a year is non-vintage: click Edit on the integration.

Two years in one item

The product carries two different years, or a year next to a non-vintage marker, so Vinius cannot tell which is the vintage. Keep one year in the name. A year that is not the vintage, such as a founding year, can stay when you set the vintage as an attribute: the attribute wins over the name.

No bottle size

Vinius found no bottle size, and the rule A wine without a bottle size is a 75 cl bottle is off. Add the size to the name (75cl, 0,75 l, 1,5 L, magnum) or as an attribute named Size. Or turn the rule back on.

Style unclear

Vinius could not tell whether the wine is red, white, rosé, sparkling, dessert or fortified. Put the wine in a webshop category that names the style, such as Red wine, or add a product tag that does.

Title not readable

Vinius could not read the product name. This can be a passing problem on the Vinius side, so run the check again first. If the same products come back every time, contact Vinius.

SKU appears twice

Two or more products in the feed share one product code. All of them are left out, and the check Every SKU appears once fails. Usually two variants share one Internal Reference in Odoo: give each its own.

Products set aside as not wine

Vinius takes wine from the feed and nothing else, for now. Products set aside here do not count as wines, so they do not count against the 90% either.

Not wine

Glassware, carafes, corkscrews, gift boxes, vouchers, tastings and other accessories. Vinius recognises them by words in the product name or the webshop category, in several languages.

A real wine lands here when its name or category contains such a word. A gift box with a wine inside is read as wine when its name carries a standard bottle size, such as 75cl. Otherwise take the word out of the name, and check that the wine does not sit in a category such as Glasses or Gift boxes.

Spirit

Whisky, gin, rum, cognac, grappa, liqueurs and other spirits. Leave their categories out of the Vinius feed.

Beer or cider

Beer and cider. Leave their categories out of the Vinius feed, as with spirits.

Warnings

A wine with a warning is published. The warning points at something you may want to fix.

75 cl assumed

Vinius found no bottle size and took 75 cl, as the rule A wine without a bottle size is a 75 cl bottle allows. Look through the list: a magnum or a half bottle among them is now listed as 75 cl. Add the size to the name, or as an attribute named Size.

Non-vintage assumed

Vinius found no year and treated the wine as non-vintage, because the rule A wine without a year is non-vintage is on. Check that every wine in this list really is non-vintage.

No EAN

The product has no barcode. The wine is published all the same. Fill in Barcode in Odoo where you have one: Vinius keeps the EAN with your offer.

EAN not valid

The barcode has the wrong length or a wrong check digit, so Vinius publishes the wine without it. Correct the Barcode in Odoo, looking for a typo or a missing digit.

Price not plausible

You declared a trade price, and this one is below €1 or above €5,000 a bottle excl. VAT. The wine is published without a price. It may be a price per case, a placeholder price or a typo: correct it in the feed's pricelist in Odoo. With Trade price incl. VAT, check the VAT rate too, since Vinius takes it off first.

Country unclear

Vinius could not tell the wine's country from its name. A wine Vinius already knows is published as usual. A wine new to Vinius is not published without a country. Add the appellation or the region to the product name.

Uncertain reading

The language model that splits the name was not sure of its answer. Check what Vinius read in the report. A name in the order producer, wine, appellation, vintage, size reads best.

Producer unclear

The wine's name points to a different producer than the one Vinius read, for example because a Producer attribute disagrees with the name. Make the attribute and the name agree.

Same wine twice

Two products matched the same wine, vintage and bottle size. That is often right, for example a single bottle and a case of six of the same wine. If it is not, one of the two names is wrong.

The result per wine

On every sync

Every scheduled sync, and every Sync now, runs the integrity check again. It also compares the result with what buyers see today. A sync that trips one of these guards is held: you see This sync is on hold, and nothing is published.

The limits for shares only apply from ten wines, or ten prices, upwards. Check the report, then click Apply anyway to publish the sync as it stands, or Discard to drop it. Until then, buyers keep seeing the previous state.

Published, and not published

After each applied sync, Published shows what changed: New offers, Offers updated, No longer listed, Wines new to Vinius, New vintages and Prices recorded. Not published counts the wines that passed the check but did not go live, with a reason:

Related guides

• Bringing your catalogue into Vinius
• Connecting your Odoo product feed