PIM for Food Wholesale

Yes. Model them so kitchens can use them. Use one multi-select field for the allergens a product contains and a separate one for "may contain", because a precautionary statement is not a declaration and chefs handle the two differently. Hold nutrition per 100 g or 100 ml in numeric fields with units, the basis the regulation uses. Keep the ingredient statement as text and the supplier's specification PDF in a file field on the same item. Mark the fields required on the family and add a Quality Guard rule that holds back items where they are empty.

Not as an import. WISEPIM imports CSV, Excel and XML, so first ask each supplier for the spreadsheet or data pool export behind the PDF. When a supplier only sends PDFs, attach the PDF to the item in a file field and enter the values once. Quality Guard then checks those values before every export, and the source document stays next to them for your QA team.

No software does that for you: the food business stays responsible for its food information. WISEPIM keeps the particulars you pass on in one place, checks them for gaps and contradictions before export, and keeps a history of field changes.

No. WISEPIM tests the GS1 check digit of GTIN-8, GTIN-12, GTIN-13 and GTIN-14 codes and flags duplicates, but it does not look codes up in a GS1 registry and it is not a GDSN data pool. You can import an export from your data pool as CSV, Excel or XML, and adopt GS1 GPC bricks into your category tree.

Keep units per case, the case GTIN, net and gross weight, dimensions and cases per pallet as attributes with units on the item you sell. Then add two Quality Guard rules. A formula rule (units per case × unit net weight matches the case net weight, within 1%) catches a wrong pack size. A ratio rule (case gross weight divided by case net weight between 1.0 and 1.3) catches swapped columns. The GTIN check digit rule works on the unit GTIN and the case GTIN alike.

WISEPIM has no separate packaging hierarchy. Keep one item per unit you sell, each with its own GTIN, and hold the pack data inside it as attributes, such as units per case and the case GTIN. Formula rules then check that the numbers on each item agree. If your ERP has one article number per unit, mirror that in WISEPIM.

AI can propose an allergen list from the ingredient text your supplier sent, but allergen data carries legal weight, so treat it as a draft. Set the allergen and ingredient fields to "Ask me" in AI review, and every AI proposal waits for a person in the Review inbox. AI quality review also screens for items where the allergen field and the ingredient list disagree.

Yes. Give purchasing and content a custom role that cannot edit the allergen, ingredient and nutrition attributes, and keep the edit rights on them with QA. The server checks those rights on every save. Set the same fields to "Ask me" in AI review, and every AI proposal for them waits in the Review inbox until a person accepts it.

No. Your ERP stays the system of record for orders, stock and prices. There is no ERP connector: item data comes in from ERP exports as CSV, Excel or XML, on a schedule with automations from the Business plan, and stock and price files can arrive through supplier sources by link, FTP, SFTP or email. API access starts on the Pro plan.

Probably not. The PIM for grocery page covers supermarkets and online grocery retail: shelf copy, reformulations and consumer channels. This page is for wholesalers and suppliers whose customers are kitchens, caterers and shops, where case data, ordering portals and customer files matter as much as the description.

WISEPIM is free up to 100 products. Paid plans are priced by product count, and every plan includes unlimited users. Quality Guard and automations start on the Business plan, API access on Pro. The pricing page lists every tier.