If you have ever submitted a new item form to UNFI or KeHE and gotten a rejection because your case dimensions did not match your data pool record, you have already met GDSN. The Global Data Synchronization Network is the plumbing that moves your product attributes (weights, dimensions, ingredients, allergens, images) from your systems into your distributors' systems and out to retailers. When it works, your new items launch on schedule. When it breaks, you get slotting holds, chargebacks, and a category manager who stops returning calls.
For CPG brands selling through UNFI, KeHE, and most major retailers, GDSN is no longer optional. It is the price of admission. And yet most founders learn about it the hard way, the week before their first shipment, when a data sync error blocks their product from being assigned a warehouse slot. This guide walks you through what GDSN is, how to set it up, and how to keep it clean so it does not cost you margin.
What GDSN Is and Why Distributors Require It
GDSN stands for Global Data Synchronization Network. It is a global standard, governed by GS1, for how brands publish product attribute data and how trading partners (distributors, retailers) subscribe to that data. The whole point is to ensure that the product specs in your system, your distributor's system, and your retailer's system are identical and updated in real time.
Before GDSN existed, every brand sent every retailer a different spreadsheet for every new item. UNFI had a new item form. Whole Foods had a different form. Sprouts had another. Data drift was constant. A brand would update a case weight in one system, forget the others, and end up with mismatched records that triggered receiving errors and deductions.
GDSN solves that by making the brand publish one canonical record to a "data pool," which then syndicates the data to every subscribed trading partner. Update the case weight in your data pool, and UNFI, KeHE, Whole Foods, Sprouts, and anyone else subscribed to your GTIN sees the change automatically.
UNFI and KeHE both require GDSN for new item setup. KeHE has been particularly aggressive about enforcing GDSN compliance, holding new items in pending status until data passes validation. UNFI's New Item Form (NIF) process pulls data directly from your GDSN record. If your record is incomplete or invalid, your item does not get set up. Period.
GDSN is not a nice-to-have. It is the data backbone that determines whether your product can be received, slotted, and sold at scale. Brands that treat GDSN as an afterthought lose weeks of shelf time waiting for sync errors to resolve.
The GDSN Ecosystem (GS1, Data Pools, and Trading Partners)
Three players matter when you think about GDSN. Understanding the role each plays makes setup far less confusing.
GS1 is the standards body. They define the rules for how product data is structured, what attributes are mandatory, and how GTINs (Global Trade Item Numbers, the formal name for barcodes) are assigned. You join GS1 to get your company prefix, which is the unique numeric identifier that becomes the first digits of every GTIN you create. GS1 US is the relevant body for brands selling in the United States.
Data pools are the platforms where you actually publish and maintain your product data. The two major data pools serving North American CPG are 1WorldSync and Syndigo. Both connect to the GDSN network, both syndicate to UNFI, KeHE, Whole Foods, Walmart, Target, Kroger, and Amazon, and both charge subscription fees. 1WorldSync is the legacy player with deep distributor integrations. Syndigo (which absorbed Edgenet and Riversand) has invested heavily in digital shelf and image management. Either works for most brands.
Trading partners are the distributors and retailers who subscribe to your data through their own data pool or GDSN integration. UNFI and KeHE pull from both 1WorldSync and Syndigo. Whole Foods, Sprouts, Wegmans, Walmart, Target, and Kroger all subscribe via GDSN. When you publish a record, you specify which trading partners to syndicate it to.
The simplified flow looks like this. You join GS1 and get a company prefix. You assign GTINs to each of your products and their cases. You subscribe to a data pool (1WorldSync or Syndigo) and upload your product attributes. You publish those records to your trading partners. They receive the data automatically and use it to set up your items in their systems.
1WorldSync alone serves more than 50,000 brands and connects to most major North American grocery retailers. Your data pool subscription is what gives you access to that distribution network. Without it, you are submitting paper forms one retailer at a time.
Step by Step GDSN Setup for a New CPG Brand
Setting up GDSN takes 4 to 8 weeks for most brands. Plan ahead. Do not start this work the month you want to launch in retail.
Step 1. Join GS1 US and get your company prefix. Apply at gs1us.org. The annual fee is based on the number of GTINs you need. For a brand with 5 to 25 SKUs, expect $250 to $1,050 in annual GS1 dues. Your company prefix is the foundation for every GTIN you assign. Do not borrow a prefix from a co-packer or another brand. You need your own.
Step 2. Assign GTINs to every product, every case, and every pallet. Each consumer unit gets a GTIN-12 (the standard UPC). Each case gets a GTIN-14 (also called an ITF-14 or SCC-14). Each pallet, if you sell at pallet quantities, needs its own GTIN. Mistakes here cascade. If you reuse a GTIN across two products or two case packs, your records will fail validation at every trading partner.
Step 3. Choose a data pool and subscribe. 1WorldSync and Syndigo are the main options. Both charge annual subscription fees that scale with the number of GTINs and trading partners. Expect $1,500 to $5,000 per year for a small brand, more as you grow. Ask each vendor for a demo, a fee schedule, and a list of trading partners they syndicate to. Both support UNFI and KeHE.
Step 4. Gather your mandatory attributes. GDSN requires a baseline set of data for every product. Brand name, product description, GTIN, case pack configuration, net content, gross weight, net weight, length, width, height, country of origin, ingredients statement, allergen declarations, nutrition facts, and product images (typically a standard front-of-pack image at specified dimensions). Mandatory attributes vary slightly by target market and product category.
Step 5. Gather your optional but increasingly expected attributes. Dietary flags (gluten-free, vegan, organic, kosher, non-GMO), claims, certifications, marketing copy, secondary images, ingredient origin data, and sustainability attributes. Optional today often becomes mandatory tomorrow. Whole Foods has been steadily expanding its required attribute list. Walmart pushes hard on digital shelf attributes. Build the full record once.
Step 6. Publish to your trading partners. Inside your data pool, select which trading partners to syndicate each GTIN to. UNFI, KeHE, and your target retailers will receive the data and confirm receipt. Watch for validation errors in the response messages and resolve them before they hold up new item setup.
Build a master attribute spreadsheet before you touch the data pool. Every GTIN, every dimension, every nutrition fact, every allergen, every image URL in one source-of-truth file. Loading data directly into 1WorldSync or Syndigo without a master file means you will have no way to audit drift later. The master spreadsheet is also what you hand to a new ops hire on day one.
Common GDSN Errors and How to Troubleshoot Them
Even brands with clean data hit GDSN errors. The trick is recognizing them quickly and fixing them before they trigger distributor rejections.
Mismatched weights and dimensions. This is the most common GDSN error. Your case is listed as 10 lbs in your data pool but ships as 10.4 lbs on the actual scale. Receiving teams catch the discrepancy and either reject the load or charge you a deduction. Fix by physically weighing and measuring every case configuration with a calibrated scale, then updating your data pool record. Never estimate. Never copy weights from a spec sheet that was written before the final formulation.
Missing or invalid nutrition data. GDSN requires structured nutrition data, not a photo of the panel. If your nutrition facts are missing a required field (often serving size in grams or specific micronutrients required by recent FDA labeling rules), your record fails validation. Fix by working through every nutrition attribute systematically and confirming that values match your physical label exactly.
Image URL failures. Data pools require product images to be hosted at specific URLs in specific formats and dimensions. If your image URL returns a 404, redirects, or serves the wrong format, syndication fails silently. Your trading partner ends up with no product image, which delays digital shelf setup and can block e-commerce listings. Fix by hosting images on a stable URL (your own domain or a CDN you control, not a marketing agency that might lose access).
Allergen and ingredient inconsistencies. Allergens declared on your physical label must match allergens flagged in your GDSN record. Brands often update a formulation, change the label, and forget to update the data pool. The result is a label that says "contains soy" while the data pool record says no soy. Major retailers catch this and reject. Fix by treating GDSN updates as a required step in your label change checklist.
Validation rejects from specific trading partners. Each retailer has its own additional validation rules on top of the base GDSN standard. Whole Foods requires more dietary attributes than UNFI. Walmart requires more digital shelf content. When you syndicate to a new trading partner, expect a fresh round of validation errors specific to that retailer. Read the rejection message carefully. The error code usually tells you which attribute is missing or invalid.
Founders treat GDSN as a one-time setup and never touch it again. Then they reformulate, switch co-packers, change case quantities, or update packaging, and the data pool record stays frozen in time. Every product change is a GDSN update. Build that into your change management process from day one.
How Clean GDSN Data Prevents Deductions and Slotting Holds
The brands that take GDSN seriously do not just avoid setup pain. They protect margin every single month.
Deduction prevention. A meaningful portion of distributor deductions trace back to data discrepancies. Cases that weigh more than what is on the record incur freight overage charges. Cases that arrive with different dimensions than what is in the warehouse management system cause pallet build errors and slot misallocation. Both generate operational deductions. Clean GDSN data means clean receiving, which means fewer deductions.
Slotting hold prevention. When you launch a new item, the distributor assigns it a warehouse slot. That slot is sized based on the case dimensions in your data pool record. If the dimensions are wrong, the case will not fit the slot, and your item gets held until ops manually re-slots it. Multi-week slotting holds delay first shipments, which delays first orders, which can blow your forecast and damage your launch.
Store-level shelf issues. Retailers use GDSN data to feed their shelf planning tools, planograms, and shelf-edge labels. If your dimensions are wrong, the planogram space allocated to your product will be wrong, leading to overhangs, gaps, or product getting cut from the set entirely. The category manager does not always know it was a data problem. They just see a brand that "does not fit the shelf."
Buyer trust. Buyers notice when a brand consistently delivers clean data. It signals operational maturity. A founder who fumbles through GDSN questions in a category review looks like a beginner, even if the product is excellent. A founder who can walk through their GDSN attribute coverage in two minutes looks ready for a multi-region expansion.
The week we cleaned up our GDSN record was the week our UNFI deductions dropped by about a third. We were paying for data errors for two years without realizing it.
Clean GDSN data keeps your existing accounts profitable, but the bigger lever is getting in front of the next set of buyers who will subscribe to that data.
Opener finds best-fit retailers, verifies buyer contacts, and runs personalized outreach on autopilot, so your team focuses on growth while your data backbone runs clean.
Book a DemoThe Real Cost of GDSN (Budget Honestly)
Founders underestimate the cost and time required to run GDSN well. Plan for both.
Direct costs. GS1 membership runs $250 to $1,050 per year for small brands and scales with GTIN count. Data pool subscriptions (1WorldSync or Syndigo) typically run $1,500 to $5,000 per year for small brands and can climb to $15,000+ for larger portfolios with many trading partners. Some data pools charge per trading partner connection, so syndicating to more retailers costs more.
Internal time. Initial setup takes 40 to 80 hours of focused work for a brand with 5 to 25 SKUs: gathering attributes, weighing cases, photographing products, formatting nutrition data, loading the records, and resolving validation errors. Ongoing maintenance runs 4 to 10 hours per month if you are actively launching new items or making formulation changes.
Outsourced help. Many brands hire a GDSN consultant or contract operator to handle initial setup and ongoing maintenance. Expect $2,000 to $8,000 for initial setup and $500 to $1,500 per month for ongoing management, depending on portfolio complexity. For brands launching into UNFI or KeHE for the first time, outsourcing the initial setup can be worth every dollar.
Cost of not doing it. A single new item rejection at UNFI or KeHE because of bad GDSN data can delay your launch by 4 to 8 weeks. If that delay misses a buyer's category reset window, you lose a full season. For a brand projecting $200K in first-year velocity at a chain, that delay can cost $30K to $50K in lost revenue. Compared to the cost of doing GDSN right, the math is not close.
When you negotiate your first data pool subscription, ask explicitly for a list of "trading partners included" versus "trading partners that require additional fees." Pricing models vary, and a subscription that looks cheap upfront can balloon when you add Walmart, Target, or Whole Foods syndication.
Answering the Founder Questions
"What is GDSN and do I need it?" GDSN is the data network that syncs your product attributes from your records to your distributors and retailers. If you sell through UNFI, KeHE, Whole Foods, Sprouts, Walmart, Target, Kroger, or Amazon, you need it. If you are direct-to-consumer only, you do not. Most CPG brands cross the GDSN threshold the moment they say yes to their first distributor.
"How do I sync my product data with UNFI via GDSN?" Join GS1, assign GTINs, subscribe to 1WorldSync or Syndigo, build a complete attribute record for every SKU, and publish to UNFI as a trading partner. UNFI will pull your record into their New Item Form workflow. Errors come back through your data pool as validation messages. Resolve them, republish, and your item moves to active setup.
The brands that win in modern wholesale treat GDSN as core infrastructure, not an IT chore. Clean data is how you launch on time, get warm inbound from buyers who trust your specs, and protect margin from the deductions that bad data triggers. Get the foundation right once and you stop paying the tax forever.
Opener helps CPG brands identify best-fit retail accounts, find verified buyer contacts, and run personalized outreach on autopilot.
Book a Demo