Product data wholesale online

Key points

Good product data makes it easier for business customers to find and order the right product. You do not need to start a major systems project to achieve this.

• Bring basic, commercial and logistical data together in a clear product structure.
• Give customers enough information to assess and compare products.
• Agree where data is managed and who updates it.
• Start with items where errors or missing information have the greatest impact.
• Measure changes in data quality and in the ordering process.

What product data means for an online wholesaler

If you sell online, product data is more than a name and a price. The information partly determines how customers find, compare and order items. It also helps employees work with the same data. It is therefore useful to first clarify what information you manage and who it is intended for.

What product data includes

Product data comprises all the information that allows you to identify, present and process an item. This includes a product code, product name, description, dimensions, material and available variants. The information required depends on your range and the questions customers ask.

You could organise the different types of information as follows:

The table is a starting point, not a universal standard. By specifying the fields required for each product group, you can avoid making customers search through an unnecessary amount of information to make a simple choice.

The difference between basic, commercial and logistical information

Basic information clarifies which product is involved; commercial information helps your customer decide on the terms under which they can buy it. Logistical data then supports order processing and delivery. In practice, these categories sometimes overlap, but each has a different purpose.

A product name or product code, for example, is not the same as a minimum order quantity or pack size. If you only keep the latter information in an internal note, the online shop may present a different picture from your sales team. A clear classification makes such differences easier to spot.

Product data for customers, employees and sales channels

Your customers use product information to make a choice, while employees may need the same data for advice, sales and order fulfilment. An online shop or other sales channel must also be able to display the information in a useful way. This does not always require exactly the same presentation, but it does require clarity about which data is authoritative.

If you are still preparing to move into online sales, targeted preparation for your online shop can help you think through your product range, systems and fulfilment in advance. This helps prevent you from structuring your product information only when the online shop is already due to be populated.

Why product data matters for online sales

In a face-to-face sales environment, an employee can explain or show a product. Online, your product information has to do more of that work. Missing details can cause uncertainty, while unclear data can also lead to additional internal checks. With a good foundation, you make it easier for people to find, assess and order products correctly.

How complete product information reduces uncertainty for business buyers

Business buyers often want to know whether an item suits their application, packaging and ordering process. A clear description with relevant specifications answers their questions before they need to get in touch. This does not mean every product needs a long description: the focus is on information that matters to the decision.

You can start with the questions your sales team gets most often. If customers regularly call about dimensions, compatibility or pack contents, this suggests that the information is missing from the product page or difficult to find. This makes clear product information a practical part of your service.

The impact on findability and filters in the online shop

Filters are only useful if the attributes behind them are entered consistently. When the same attribute is recorded in different ways, products may disappear from the results or appear under an unexpected filter value. This makes it harder for customers to find a suitable item.

It is therefore worth considering standard values and naming conventions for the attributes customers use to search. A filter for size, material or application only works well if your catalogue includes those attributes consistently and in sufficient detail. The product structure is therefore also a practical prerequisite for a useful online shop catalogue.

Fewer errors in ordering, stock and delivery

Product information can also help prevent errors by making clear exactly what a customer is ordering. Unit, pack size and minimum order quantity are important, for example, if an item is not sold individually. If this information is missing or contradictory, the risk of misunderstandings and manual corrections increases.

So do not look only at the product page. Also check whether the data customers see matches the information employees use when processing orders. If you are changing a catalogue or ordering process, the experience of a B2B product page can offer useful pointers for presenting purchase information clearly.

Common objections to investing in product data

Improving product data is not always high on the priority list. Often, the information seems to be there already, or there are concerns about time, cost and technology. The focus here is C - Objections: the specific reasons why you are putting off the investment. These are business considerations, not formal procedural objections, and they are most compelling when you assess them against your own ordering process.

“Our customers already know the products”

Regular customers may know the range, but that does not mean they know every detail by heart. A new employee, buyer or customer searching online for an item may not have personal knowledge to fall back on. Product information is also a useful tool for existing customers who want to reorder quickly.

So you do not need to explain everything as if the customer has never seen the product before. Focus on information that supports a purchase decision and on details that help identify the right item. This keeps the presentation concise and useful.

“Maintaining product information takes too much time”

Updating data manually can take time, especially if information is entered in several places. But doing nothing can also create work: employees look up answers, check orders or correct inconsistent data. So first identify where the greatest effort is being spent.

A brief review could answer questions such as:

• Which product groups often prompt customer questions?
• Which data is currently maintained in several places?
• Where are errors or corrections most often discovered?
• What product information is missing for online sales?

With these answers, you can prioritise tasks instead of tackling the entire catalogue at once. A small, clearly defined improvement is often easier to plan and assess than a broad project with no clear first step.

“Our ERP or online shop software already handles this”

Software can store and transfer information, but that does not automatically mean every field is complete, up to date or suitable for every audience. It helps to investigate what data the system contains, which source is authoritative and what the customer ultimately sees. This helps you find out whether the issue lies in the data, the configuration or the transfer.

For example, an online shop may display a product name while important usage attributes are missing. An ERP system may manage stock data without containing all the commercial information needed for your product page. So map out the roles of your systems before concluding that additional data management is unnecessary.

“A PIM system is too expensive or complicated”

Not every wholesaler immediately needs a separate system to improve product information. The first step could simply be clear field names, an agreed source and an overview of missing data. Only once you know where the current approach falls short can you assess whether you need different tools.

Consider the size of your product range, the number of sales channels and the amount of manual work involved. This allows you to compare an investment not with an abstract ideal of perfect data management, but with the situation you actually want to improve.

What good product data includes for wholesalers

Good product data is not simply about collecting as much information as possible. The data needs to suit your range, your customers’ expectations and the way you sell. Technical attributes are decisive for some items; for others, packaging or certification plays a bigger role. A useful standard makes room for these differences.

Product specifications, attributes and variants

Specifications clarify what a product can do, what it is made of or what size it is. Attributes can help customers filter and compare products. Variant-specific details, such as colour or size, must remain clearly linked to the right item.

A customer can only make a clear choice of variant when the information shown matches what they are ordering. So check that attributes use consistent names and that variant details remain linked to the main product. A consistent structure makes your catalogue easier to manage for both people and systems.

Prices, stock and minimum order quantities

Price, stock status and minimum order quantity together determine whether a customer can place an order as expected. Not every customer needs to see the same price or terms, but differences must be managed carefully and displayed correctly. Pack size also deserves attention if orders are not processed by individual item.

Record which data changes frequently and who is responsible for keeping it up to date. This makes it easier to decide which information is updated automatically and which requires an employee to check it. This prevents a fixed product description from being confused with data that can change daily.

Images, documents and certifications

Images help customers identify and assess an item. Documents and certifications can provide additional information when relevant to the purchase, application or internal assessment. Make sure files are linked to the right product or variant and are easy to find.

Also check that customers understand exactly what a document relates to. A file that is not clearly linked to a product may cause more confusion than it resolves. Good findability and clear naming conventions make the material more useful.

Mandatory and industry-specific product information

Depending on your product range, specific information may be needed to present or sell products responsibly. The exact requirements differ by product and sector, so do not treat a general list as a substitute for checking the rules that apply to your items. Involve colleagues responsible for compliance or product safety where necessary.

Then make clear which data is mandatory for each product group and who checks it. This makes industry-specific information part of the process, rather than a one-off task that only comes up when a customer asks about it.

Managing and sharing product data with systems and customers

Once you use information in several places, management becomes more important than simply entering it. Product data may be managed in an ERP system, displayed in an online shop and shared with customers or other channels. The risk arises when it is unclear which version is correct. A simple agreement on ownership and exchange already helps reduce that risk.

The role of ERP, PIM and the online shop

Systems can have different roles. An ERP system can support operational data, a PIM system can manage product information centrally, and an online shop can present information to customers. The right division of responsibilities for you depends on your processes and existing setup.

For each type of data, make clear where the source is and how the information is sent to other systems. This means you do not have to expect one application to perform every function. If you change the catalogue structure, it is also advisable to test how the change affects the online shop and day-to-day order processing.

Sharing product information with customers and marketplaces

Customers and sales channels may need different information formats or presentations. This makes it useful to structure the underlying data well, so you do not have to look up the same information again for each channel. Think in advance about which fields can or must be shared and how you will check that they are up to date.

In one case study, Zinzo migrated more than 1,500 Shopify product variants for Sjeng Sports to a native multi-variant structure, with no stock discrepancies or prolonged downtime. The Sjeng Sports migration shows why product structure needs attention when transferring data to a different model.

Preventing data from diverging between systems

Differences often arise gradually: an employee updates a description in the online shop while the source information remains unchanged. If this approach is repeated, it becomes harder to determine which value is authoritative. Agreeing a source for each field and defining a clear process for changes can help prevent this problem.

You can first track a change for a small group of items and check whether all relevant systems receive the same information. This is a practical way to make the impact visible before applying the approach more widely.

Improving product data without an unnecessarily large project

You do not have to wait until every product is perfect before making improvements. A manageable start will show which data is missing, where inconsistencies exist and which product groups should take priority. Choose an approach that fits your team’s available time. This makes product data management a workable routine rather than a one-off clean-up exercise.

Starting with the products that will deliver the greatest benefit

Start with products that customers often ask about, that lead to noticeable ordering errors or that are important to your online range. You do not have to choose on instinct: use sales data, customer enquiries and feedback from employees to make an initial selection. This focuses attention on problems you can observe.

A structured Store Audit can show where an online shop is underperforming commercially and which areas need attention. Use this kind of analysis to inform your priorities, not as a reason to automatically review every product at once.

Finding missing and inconsistent data

Compare a sample of product pages with the information employees use in their day-to-day systems. Look for blank fields, different units, duplicate values and descriptions that no longer match the item. Checking a limited number of products can already reveal patterns in your data management.

Record your findings in a way your team can act on. A list of products, missing fields, sources and owners is often enough to assign the first corrections. You can then decide whether a structural change to data entry or systems is needed.

Agreeing ownership and maintenance within the team

Product data remains more reliable when it is clear who can add information, who checks changes and who is responsible for periodic maintenance. This does not have to mean creating a separate role. The team does need to know who to contact with a question or discrepancy.

Also agree when data should be checked again, for example after a change to packaging or the product range. This prevents a product page from gradually becoming outdated without anyone noticing. A small, regular routine is often easier to maintain than a major clean-up that then loses momentum.

Automating step by step where it saves time

Automation is most useful when a recurring task is clearly defined and the data is supplied reliably. So do not start by automating an unclear process. First map out what information is transferred, what checks are needed and where exceptions occur.

For Loints of Holland, Zinzo built a custom Shopify B2B pre-order app that allows retailers to reserve stock for the next season and makes demand visible for forecasting. The Loints of Holland case study is an example of a bespoke solution for a specific ordering process, not a general solution to every data management problem.

Assessing the results of better product data

Improvements are only convincing when you can see what has changed. Start with a baseline and choose a few measurements that align with your goal. That goal may relate to data quality, but also to fewer corrections or a clearer ordering process. Compare results over a suitable period and take other changes in your online shop into account.

Measuring the completeness and currency of product information

For each product group, choose the fields that customers or employees need and measure how many products include this information. Also look at how up to date changing data, such as stock or prices, is. A high percentage of completed fields means little on its own if the information is incorrect.

A sample helps you assess completeness and accuracy side by side. Keep the measurement method consistent when you check again later. This allows you to see whether the improvement came from a different way of working, rather than a changed definition of what counts as complete.

Tracking errors, returns and customer service enquiries

Track the questions customers ask and the corrections the team makes before and after updating product information. Look for recurring product groups or fields. This helps you distinguish between general improvement and a specific cause that still needs attention.

Returns can also indicate unclear product information, but they are not automatically a data problem. So check the reason for a return and whether it relates to, for example, size, application or packaging. This prevents you from attributing a change to product data without sufficient evidence.

Comparing conversion and use of online shop filters

You can track conversion and filter usage around an update to product information, but make sure you compare similar periods and product groups. Changes in traffic, product range or price can also affect the outcome. So do not look at just one overall figure.

If filter use increases but customers still drop out, this may indicate that the filters are easier to find but the product information still does not answer enough questions. So combine figures with observations from customer service and sales. This gives you a more useful picture of what your next step should be.

In conclusion

Good product data is a practical foundation for an online shop that helps customers choose and employees work accurately. Start with the information that matters most for your range and ordering process, assign ownership and measure what changes. If you would like to discuss which technical improvements are right for your online shop, book a conversation with Zinzo.

Frequently asked questions

What is product data?

Product data is the information you use to identify, describe, present and sell products. This includes product codes, attributes, prices, packaging and logistical data.

Which product data is most important for a wholesaler?

That depends on the range. Start with the data customers need to find, assess and order items, such as specifications, variants and minimum order quantities.

Do you need to complete all product information at once?

No. You can start with product groups where missing or inconsistent data most often leads to questions, errors or extra work.

Is a PIM system always necessary?

No. A PIM system may suit certain processes and scales, but you can first establish where your current management approach falls short and what improvements are needed.

How can you prevent inconsistent information between systems?

Assign an authoritative source for each type of data and define how changes are transferred and checked. Test the exchange with a small group of products before applying it more widely.

How often should you check product data?

That depends on how quickly the data changes and how important it is to ordering and delivery. Agree an appropriate review schedule for each type of data.

How can you tell whether better product data is delivering results?

For example, measure completeness, corrections, customer enquiries and the use of online shop filters. Compare the results with an earlier baseline and take account of other changes that may affect them.