Product data & PIM
Business Central, GS1, GDSN, and Syndigo: Getting Product Data to Market
How an upstream product-data process can prepare accurate, approved information for trading partners without confusing the roles of ERP, PIM, and syndication.
An item can be ready for purchasing and inventory inside an ERP system while still missing information a distributor needs to list it. The internal item number may be correct. The packaging hierarchy, product images, market-specific description, or approved specification may be incomplete.
For a manufacturer using Microsoft Dynamics 365 Business Central, the useful question is where each fact should be maintained and how it reaches the next system. Adding a product-information management layer, or extending the Item Card, can help organize upstream work. It does not remove the need to satisfy a recipient’s requirements or operate the downstream publishing process.
Understand the jobs in the chain
Business Central supports the company’s operational records. An implementation may use item records, units of measure, and additional fields or related tables. Microsoft’s extension model allows developers to extend eligible tables and pages. The right design depends on the business’s installed extensions and current data ownership.
Product information management, or PIM, is the discipline and supporting tooling for organizing, enriching, reviewing, and distributing product content. A PIM does not have to become the authority for every field. For example, an approved product specification may be owned by quality while inventory remains in ERP.
GS1 standards and GDSN provide common structures and a network for exchanging product master information. GS1 describes GDSN access through certified data pools. This is a trading-partner exchange, with processes and requirements beyond a spreadsheet export.
Syndigo provides product-content and syndication capabilities, including GDSN workflows. Its GDSN user guide directs suppliers to the recipient’s implementation guide and describes steps for item setup, packaging hierarchy, publication, and tracking recipient status. An upstream Business Central extension should prepare and govern the information needed for that process.
Start with the recipient’s requirements
Before designing fields, choose one real destination and obtain its current implementation guide. Identify required attributes, conditional requirements, permitted values, units, asset rules, and the packaging levels involved. Confirm which requirements apply to the particular product category and market.
Then map each requirement to an owner and an approved source. A field called “weight” is insufficient if one system expects net unit weight and another expects gross case weight. Record the meaning, unit, precision, and conversion rule. Test conversions against known records instead of asking a model to infer the intended interpretation.
Separate genuinely missing information from information that exists but has not been mapped. The first requires research or an owner’s decision. The second requires controlled integration work.
Use research to build evidence, not plausible values
AI can help locate candidate specifications, extract text from approved documents, compare revisions, and flag disagreements. Each proposed value should carry its source reference and remain distinguishable from an approved value.
A manufacturer page, a distributor listing, and an old sales sheet may disagree. Do not resolve that by majority vote or by choosing the most detailed paragraph. Route the conflict to the responsible owner. Safety-related, regulated, nutritional, certification, and identity fields need the appropriate authoritative review.
Keep confidential pricing and customer-specific data out of a public product-content pipeline unless there is a specific authorized destination and business reason. More complete data is not automatically data that should be shared everywhere.
A hypothetical packaging change
Illustration only: A fictional manufacturer changes a case configuration. Business Central, an internal specification, a PIM record, and a distributor listing now require coordinated attention. This is a proposed control pattern, not a report of an implemented integration.
- The product owner records the approved change and its effective date.
- The data steward checks identifier and packaging requirements against the applicable GS1 rules and recipient guidance.
- The upstream system prepares a new reviewed record, preserving the previous version.
- The integration validates fields and units before submission to the authorized syndication destination.
- The team tracks the destination’s processing and recipient status, resolves errors, and verifies the intended record reached the trading partner.
Do not treat a successful file transfer as evidence that the recipient accepted the item. Record the status the destination actually provides. Commercial listing, purchasing approval, and current availability may involve additional business steps.
Give the pilot a narrow boundary
Begin with one product family, one destination, and a named owner for exceptions. Confirm subscriptions, supported interfaces, access, field mappings, and responsibility for ongoing updates before promising an automated connection.
Use a small set containing both ordinary items and difficult cases: missing measurements, multiple packaging levels, conflicting documents, an inactive item, and a changed specification. Measure rejected records, correction time, source traceability, and recipient-confirmed completion.
A useful pilot deliverable is a reviewed mapping, a working change process, and evidence of one complete exchange. The size of the catalog is a later scaling question.
The architecture decision
Choose an enhanced Item Card when it fits the people who maintain the facts and the complexity of the content. Choose a separate PIM when channels, assets, languages, approval workflows, or product relationships warrant it. Either way, assign an authoritative owner for each field and define the outbound publishing path and how acknowledgments, corrections, and source changes return to the responsible owner.
This is upstream preparation and governance. It can complement Syndigo and GDSN rather than attempting to replace their role. Product names here identify systems and standards discussed; no affiliation, certification, or ready-made Wheeler IS connector is implied.
Sources & further reading
Primary references checked October 7, 2026. The practical recommendations and hypothetical examples are Wheeler IS editorial guidance; they are not customer results or vendor endorsements. Product capabilities and requirements can change.