@pixelsandclicks_/mcp-server 0.0.0-stage → 1.0.0
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/README.md +76 -2
- package/dist/cli.d.ts +2 -0
- package/dist/cli.js +6 -0
- package/dist/data/articles.json +1822 -0
- package/dist/data/codes.json +1230 -0
- package/dist/data.d.ts +5 -0
- package/dist/data.js +131 -0
- package/dist/search.d.ts +8 -0
- package/dist/search.js +86 -0
- package/dist/server.d.ts +2 -0
- package/dist/server.js +268 -0
- package/dist/types.d.ts +57 -0
- package/dist/types.js +1 -0
- package/package.json +45 -4
|
@@ -0,0 +1,1822 @@
|
|
|
1
|
+
[
|
|
2
|
+
{
|
|
3
|
+
"slug": "ai-forecasting-pilot-data-readiness-failures",
|
|
4
|
+
"title": "Why Your Retail CPG AI Forecasting Pilot Stalls At Day 60",
|
|
5
|
+
"description": "Three data gaps kill a CPG AI forecasting pilot before day 60: shipments read as demand, a SKU master that churned, net revenue nobody traced.",
|
|
6
|
+
"pubDate": "2026-10-01T00:00:00.000Z",
|
|
7
|
+
"author": "Pixels and Clicks",
|
|
8
|
+
"tags": [
|
|
9
|
+
"AI Forecasting",
|
|
10
|
+
"Demand Planning",
|
|
11
|
+
"Data Readiness",
|
|
12
|
+
"CPG",
|
|
13
|
+
"POS",
|
|
14
|
+
"SKU Master",
|
|
15
|
+
"Returns"
|
|
16
|
+
],
|
|
17
|
+
"readingTime": 9,
|
|
18
|
+
"cluster": "forecasting",
|
|
19
|
+
"hub": "supplier-scorecard-for-cpg-suppliers",
|
|
20
|
+
"draft": false,
|
|
21
|
+
"hideToc": true,
|
|
22
|
+
"image": "/images/articles/ai-forecasting-pilot-data-readiness-failures-banner.jpg",
|
|
23
|
+
"imageAlt": "What a CPG AI forecasting pilot needs that a shipment-only dataset cannot give it: weekly POS, a stable SKU master, and a net-of-returns revenue signal",
|
|
24
|
+
"answer": "An AI forecasting pilot stalls when the data feeding the model does not describe demand. Three failures account for most of it: shipment data substituted for POS, a SKU master that turned over during the training window, and gross-ship numbers that ignore returns and deduction leakage. The model is not wrong. The signal is.",
|
|
25
|
+
"answerQualifier": "Based on McKinsey research on digital pilot purgatory, McKinsey's State of Food and Beverage data on new-item share of sales at mid-market CPG, Overdeduct and Inmar benchmarks on retail-deduction load, practitioner commentary from TrueGradient and Impact Analytics on AI-forecasting data quality, the bullwhip-effect research from Hau Lee et al. in Sloan Management Review, and public retailer data programs (Walmart Luminate, Amazon Vendor Central). October 2026.",
|
|
26
|
+
"faq": [
|
|
27
|
+
{
|
|
28
|
+
"q": "Why does an AI forecasting pilot miss on exactly the SKUs that matter most?",
|
|
29
|
+
"a": "The pilot usually misses on your fastest movers and your promoted SKUs. Both share a data gap. A fast mover with a recent stockout trains the model on a demand number lower than real demand. A promoted SKU with no flag in the data trains the model on a baseline inflated by lift. Both failures look like model error on the dashboard. Both are data problems upstream of the model."
|
|
30
|
+
},
|
|
31
|
+
{
|
|
32
|
+
"q": "Can I run an AI forecasting pilot on shipment history alone?",
|
|
33
|
+
"a": "You can run it. The model will fit the shipment pattern. The forecast will miss sell-through turns by whatever time it takes the retailer to reorder, which is one to four weeks for most CPG categories. Pilots run on shipment-only data commonly show acceptable in-sample accuracy during training and lose it when the retailer's order cadence shifts. If you have access to Walmart Luminate, Target Mindset, or Amazon Vendor Central POS, pull it before the pilot starts."
|
|
34
|
+
},
|
|
35
|
+
{
|
|
36
|
+
"q": "How much SKU turnover is too much for a forecasting pilot?",
|
|
37
|
+
"a": "McKinsey's State of Food and Beverage data shows new items drive 19 percent of sales at CPG suppliers in the $100 million to $500 million band, which implies continuous SKU addition and retirement in the training window. A pilot that treats a replaced SKU as new, and the retired one as discontinued, splits what is often one continuous demand pattern into two shorter and noisier ones. Document the SKU-replacement map before training. One field linking a new SKU to the one it replaces recovers most of the lost signal."
|
|
38
|
+
},
|
|
39
|
+
{
|
|
40
|
+
"q": "Why do my gross shipments not reconcile to my collected revenue?",
|
|
41
|
+
"a": "A CPG supplier commonly collects less than the gross shipment value after returns, deduction leakage, and reserve adjustments. Industry benchmarks from Overdeduct and Inmar put deductions and chargebacks at 2 to 15 percent of gross sales across CPG, with mid-market suppliers writing off 1.2 to 2.4 percent of gross revenue each year on unrecovered deductions alone. A forecasting model trained on gross-ship numbers forecasts volume you will not keep. Pull the net number from your AR aging or deduction register and train on that."
|
|
42
|
+
},
|
|
43
|
+
{
|
|
44
|
+
"q": "What should I audit before I commit to an AI forecasting pilot?",
|
|
45
|
+
"a": "Audit three things first. The demand signal (POS or shipment, weekly or monthly, which retailers provide what). The SKU master history (how many SKUs added, retired, or renumbered in the last 24 months, with a replacement map). And the net-revenue reconciliation (gross ships minus returns minus deductions). All three live in systems you own today. None require the pilot vendor's platform to run."
|
|
46
|
+
}
|
|
47
|
+
]
|
|
48
|
+
},
|
|
49
|
+
{
|
|
50
|
+
"slug": "amazon-1p-vendor-termination-notice",
|
|
51
|
+
"title": "The Amazon 1P Termination Notice: What 30 Days Actually Buys You",
|
|
52
|
+
"description": "An Amazon 1P termination email arrives with 30 to 60 days notice. What happens to open POs, pending claims, and the audit posture that would have caught it earlier.",
|
|
53
|
+
"pubDate": "2026-09-28T00:00:00.000Z",
|
|
54
|
+
"author": "Pixels and Clicks",
|
|
55
|
+
"tags": [
|
|
56
|
+
"Amazon Vendor Central",
|
|
57
|
+
"Vendor Terminations",
|
|
58
|
+
"1P",
|
|
59
|
+
"Net PPM",
|
|
60
|
+
"CPG",
|
|
61
|
+
"Deductions"
|
|
62
|
+
],
|
|
63
|
+
"readingTime": 9,
|
|
64
|
+
"cluster": "scoping",
|
|
65
|
+
"hub": "supplier-scorecard-for-cpg-suppliers",
|
|
66
|
+
"draft": false,
|
|
67
|
+
"hideToc": true,
|
|
68
|
+
"image": "/images/articles/amazon-1p-vendor-termination-notice-banner.jpg",
|
|
69
|
+
"imageAlt": "Amazon 1P vendor termination notice: the 90 days of data that predicted it and the audit posture that would have caught it earlier",
|
|
70
|
+
"answer": "Amazon's 1P termination notice usually gives 30 to 60 days before purchase orders stop, and the decision is almost always algorithmic once it lands. Community operators report the cut is driven by contribution margin and Net PPM, not by revenue alone. A 42% Net PPM account can be terminated if its category is competitive. Open shortage claims stay disputable inside the notice window, and your audit posture is the single lever left.",
|
|
71
|
+
"answerQualifier": "Based on r/VendorCentral community operators reporting terminations across US and EU accounts in Q2 to Q3 2026, plus public Amazon Vendor Central program guidance, September 2026. Amazon does not publish termination thresholds, so treat the specific figures below as vendor-reported patterns rather than policy.",
|
|
72
|
+
"faq": [
|
|
73
|
+
{
|
|
74
|
+
"q": "How much notice does Amazon give before terminating a 1P vendor account?",
|
|
75
|
+
"a": "Community operators on r/VendorCentral report notice periods running 30 to 60 days, occasionally two months, before Amazon stops issuing purchase orders. Some accounts get an intermediate ramp-down where PO volume drops sharply before the final cut. The termination email itself names the effective date and the last PO window. Amazon does not publish a standard notice period, so treat any figure as a data point, not a rule."
|
|
76
|
+
},
|
|
77
|
+
{
|
|
78
|
+
"q": "Can you appeal an Amazon 1P vendor termination?",
|
|
79
|
+
"a": "Rarely, and only when the decision was algorithmic rather than a Vendor Manager judgment. One recovery operator on r/VendorCentral put it plainly: it is a set decision unless you were part of an algorithmic decision and still have contact with a Vendor Manager willing to work with you, because a VM is the only role that can override the system. If a VM already flagged your account as unwilling to work on Net PPM, the appeal path is effectively closed."
|
|
80
|
+
},
|
|
81
|
+
{
|
|
82
|
+
"q": "What criteria triggers an Amazon 1P vendor termination?",
|
|
83
|
+
"a": "Vendor Managers who spoke on r/VendorCentral describe two main criteria: contribution margin for Amazon and Net PPM trend. Revenue alone does not protect an account. One operator reported a 42% Net PPM account was terminated because its category was highly competitive with many direct substitute vendors. Under-10M annual revenue accounts are reportedly a common target in the current wave. Amazon does not publish the thresholds."
|
|
84
|
+
},
|
|
85
|
+
{
|
|
86
|
+
"q": "What happens to open shortage claims after a 1P termination notice?",
|
|
87
|
+
"a": "Open shortage and chargeback disputes stay in Vendor Central through the notice window and remain disputable under Amazon's normal rules. The 30-day dispute deadline from the chargeback notification still applies. Any credit that posts before the account closes goes through the final remittance cycle. Anything filed but unresolved at closure may need to be pursued through Amazon's post-termination case queue, which multiple operators report is slower and less responsive."
|
|
88
|
+
},
|
|
89
|
+
{
|
|
90
|
+
"q": "Should you move to 3P selling after a 1P termination?",
|
|
91
|
+
"a": "Community operators are split. One vendor on r/VendorCentral reported moving to a 1P distributor and calling it a simplification. Another countered that the switch surrenders margin and brand control. The right answer depends on your category, your Net PPM at Amazon's shelf price, your non-Amazon revenue mix, and whether your brand carries independent demand. Talk to at least two operators who have made the transition in your category before deciding."
|
|
92
|
+
}
|
|
93
|
+
]
|
|
94
|
+
},
|
|
95
|
+
{
|
|
96
|
+
"slug": "amazon-closed-shortage-claims-recoverable",
|
|
97
|
+
"title": "Amazon Marked Your Shortage Claim Closed. Was It Actually Paid?",
|
|
98
|
+
"description": "A closed shortage claim in Vendor Central does not always mean the money came back. Three failure modes suppliers miss, and the 90-day re-audit that catches them.",
|
|
99
|
+
"pubDate": "2026-09-25T00:00:00.000Z",
|
|
100
|
+
"author": "Pixels and Clicks",
|
|
101
|
+
"tags": [
|
|
102
|
+
"Amazon Vendor Central",
|
|
103
|
+
"Shortage Claims",
|
|
104
|
+
"Deductions",
|
|
105
|
+
"1P",
|
|
106
|
+
"Chargebacks",
|
|
107
|
+
"CPG"
|
|
108
|
+
],
|
|
109
|
+
"readingTime": 9,
|
|
110
|
+
"cluster": "recovery",
|
|
111
|
+
"draft": false,
|
|
112
|
+
"hideToc": true,
|
|
113
|
+
"image": "/images/articles/amazon-closed-shortage-claims-recoverable-banner.jpg",
|
|
114
|
+
"imageAlt": "Auditing closed Amazon shortage claims: Vendor Central status versus what actually posted to the remittance",
|
|
115
|
+
"answer": "Amazon marks a shortage claim closed when it exits the workflow, not when a credit posts to your remittance. Three failure modes leak money past a closed status: no offsetting credit, multi-PO shortages split across claim IDs, and a post-close dispute path most vendors miss. A 90-day re-audit is the highest-ROI hour of the quarter.",
|
|
116
|
+
"answerQualifier": "Based on public Amazon Vendor Central documentation, SPS Commerce and Inmar deduction benchmarks, and community-reported patterns from 1P suppliers, September 2026. Amazon's specific dispute-window language changes periodically. Confirm current windows in your own Vendor Central case portal before writing off a claim.",
|
|
117
|
+
"faq": [
|
|
118
|
+
{
|
|
119
|
+
"q": "What does closed mean in Amazon Vendor Central?",
|
|
120
|
+
"a": "Closed means the shortage claim has exited Amazon's active workflow. The claim ID stops appearing in your open-cases queue. It does not confirm that an offsetting credit posted to your remittance. Closed is a workflow status, not a payment status. Cross-check every closed claim against remittance detail before writing it off."
|
|
121
|
+
},
|
|
122
|
+
{
|
|
123
|
+
"q": "Can you dispute an Amazon shortage claim after it's closed?",
|
|
124
|
+
"a": "Sometimes, but the mechanism changed in 2025. Amazon retired the older support-case path, and the current workflow gives you two chances only: the traditional dispute in Vendor Central, and a re-dispute if the first is denied. Community operators report the re-dispute now routes through a Contact Us case to a Tier 2 team, not the default Dispute Management button. Waiting 35 days after invoice due date before the first dispute is a widely-reported best practice."
|
|
125
|
+
},
|
|
126
|
+
{
|
|
127
|
+
"q": "How do multi-PO shortages get split across claim IDs?",
|
|
128
|
+
"a": "When one physical shipment covers multiple POs and the receiver books shortages against each PO independently, Amazon can generate one claim ID per PO. If two claims reference the same missing units from opposite sides, only one may get resolved. The other stays open, expires, or closes without payment. Look for related claim IDs before writing off any single closed claim."
|
|
129
|
+
},
|
|
130
|
+
{
|
|
131
|
+
"q": "Is a re-audit of closed shortage claims worth the time?",
|
|
132
|
+
"a": "For most 1P suppliers, yes. SPS Commerce reports that suppliers dispute only 20 to 30 percent of deductions to begin with, which leaves most closed claims unaudited. A 90-day re-audit catches the three failure modes below without needing new software. One finance analyst, one afternoon, and the remittance detail is enough to find the pattern if it's there."
|
|
133
|
+
},
|
|
134
|
+
{
|
|
135
|
+
"q": "What evidence do I need before reopening a closed claim?",
|
|
136
|
+
"a": "Match every closed claim to its remittance line. Pull the ASN transmission timestamp, the proof of delivery signed by the receiver, and any related claim IDs on the same PO. If the offsetting credit is missing on the remittance, or if the closed claim references units also disputed under a different open claim, you have grounds to reopen. Amazon reviews reopens on documentation, not on the reopen request alone."
|
|
137
|
+
}
|
|
138
|
+
]
|
|
139
|
+
},
|
|
140
|
+
{
|
|
141
|
+
"slug": "amazon-net-ppm-vs-contribution-margin",
|
|
142
|
+
"title": "Net PPM vs. Contribution Margin: How Amazon Scores Your Profitability",
|
|
143
|
+
"description": "What Net PPM, Contribution Margin, and CMLF measure, which one your vendor manager watches, and how to use all three before Annual Vendor Negotiations.",
|
|
144
|
+
"pubDate": "2026-10-21T00:00:00.000Z",
|
|
145
|
+
"author": "Pixels and Clicks",
|
|
146
|
+
"tags": [
|
|
147
|
+
"Amazon 1P",
|
|
148
|
+
"Vendor Central",
|
|
149
|
+
"Net PPM",
|
|
150
|
+
"Contribution Margin",
|
|
151
|
+
"CMLF",
|
|
152
|
+
"Profitability",
|
|
153
|
+
"AVN"
|
|
154
|
+
],
|
|
155
|
+
"readingTime": 8,
|
|
156
|
+
"cluster": "scoping",
|
|
157
|
+
"hub": "supplier-scorecard-for-cpg-suppliers",
|
|
158
|
+
"draft": false,
|
|
159
|
+
"hideToc": true,
|
|
160
|
+
"image": "/images/articles/amazon-net-ppm-vs-contribution-margin-banner.jpg",
|
|
161
|
+
"imageAlt": "Whiteboard diagram comparing Net PPM, Contribution Margin, and CMLF as three layers of Amazon vendor profitability",
|
|
162
|
+
"answer": "Net PPM (Net Pure Product Margin) is the metric your vendor manager watches. It measures Amazon's per-ASIN profit as a percentage of shipped revenue, and it drives Buy Box eligibility, PO volume, and the co-op ask at Annual Vendor Negotiations. Contribution Margin layers in Amazon's own variable costs (fulfillment, shipping, storage) and is Amazon's internal P&L view you rarely see. CMLF (likely Contribution Margin Less Funding) appears in vendor community discussions but has no confirmed public definition from Amazon.",
|
|
163
|
+
"answerQualifier": "Based on the Net PPM formula documented by Amalytix and iNymbus, Contribution Margin definitions from Calbridge Analytics and MerchantSpring, category benchmarks from MerchantSpring and SmartScout, and vendor community discussion on r/VendorCentral. October 2026.",
|
|
164
|
+
"faq": [
|
|
165
|
+
{
|
|
166
|
+
"q": "What is Net PPM and how does Amazon calculate it?",
|
|
167
|
+
"a": "Net PPM stands for Net Pure Product Margin. It is Amazon's per-ASIN profit metric for 1P vendors. The formula, per Amalytix and iNymbus: (Shipped Revenue - Shipped COGS + Vendor Terms - Sales Discount) / Shipped Revenue. Vendor Terms includes co-op accruals, damage allowances, and freight allowances. Every dollar you fund into those terms lifts Amazon's calculated Net PPM on your catalog."
|
|
168
|
+
},
|
|
169
|
+
{
|
|
170
|
+
"q": "What is Contribution Margin on Amazon and how is it different from Net PPM?",
|
|
171
|
+
"a": "Contribution Margin is Amazon's internal profitability view that layers variable costs on top of Net PPM. It subtracts fulfillment, shipping, storage, and customer service costs from the product margin. Vendors rarely see Contribution Margin directly. Net PPM is the metric that appears in your Vendor Central reports and drives the AVN conversation."
|
|
172
|
+
},
|
|
173
|
+
{
|
|
174
|
+
"q": "What does CMLF stand for in Amazon vendor discussions?",
|
|
175
|
+
"a": "CMLF appears in r/VendorCentral threads but has no confirmed public definition from Amazon. Vendor community consensus suggests it stands for Contribution Margin Less Funding, meaning Contribution Margin after subtracting the co-op and marketing allowances vendors pay. Ask your vendor manager to define the term if it appears in your negotiation materials."
|
|
176
|
+
},
|
|
177
|
+
{
|
|
178
|
+
"q": "What is a good Net PPM for Amazon vendors?",
|
|
179
|
+
"a": "Category benchmarks from MerchantSpring: hardlines 40 to 45%, softlines 30 to 37%, consumables 27 to 35%. Amazon's internal target for your catalog depends on your category average and your negotiation history. Pull your Net PPM report from Vendor Central at the ASIN level to see where you stand."
|
|
180
|
+
},
|
|
181
|
+
{
|
|
182
|
+
"q": "What happens when my Net PPM drops below Amazon's target?",
|
|
183
|
+
"a": "Amazon may reduce PO volume, restrict advertising eligibility, or flag the ASIN as CRaP (Can't Realize a Profit). At AVN, the vendor manager opens with a margin headwind claim and asks for a higher co-op accrual rate. A sustained Net PPM shortfall is one of the trajectories that can end in a 1P termination notice."
|
|
184
|
+
}
|
|
185
|
+
]
|
|
186
|
+
},
|
|
187
|
+
{
|
|
188
|
+
"slug": "bad-asn-costs-one-shipment-five-chargebacks",
|
|
189
|
+
"title": "One Bad ASN, Five Chargebacks on the Same Shipment",
|
|
190
|
+
"description": "A single EDI 856 error on one shipment triggers ASN accuracy, shortage, OTIF, routing, and invoice chargebacks. The prevention step for each.",
|
|
191
|
+
"pubDate": "2026-09-07T00:00:00.000Z",
|
|
192
|
+
"author": "Pixels and Clicks",
|
|
193
|
+
"tags": [
|
|
194
|
+
"EDI",
|
|
195
|
+
"ASN",
|
|
196
|
+
"856",
|
|
197
|
+
"Deductions",
|
|
198
|
+
"Retail Compliance",
|
|
199
|
+
"OTIF",
|
|
200
|
+
"Chargebacks"
|
|
201
|
+
],
|
|
202
|
+
"readingTime": 8,
|
|
203
|
+
"cluster": "prevention",
|
|
204
|
+
"draft": false,
|
|
205
|
+
"hideToc": true,
|
|
206
|
+
"image": "/images/articles/bad-asn-costs-one-shipment-five-chargebacks-banner.jpg",
|
|
207
|
+
"imageAlt": "One shipment branching into five chargeback types: ASN accuracy, shortage, OTIF, routing, and invoice mismatch",
|
|
208
|
+
"answer": "A single bad EDI 856 ASN can trigger five separate chargebacks from one shipment: ASN accuracy, shortage, OTIF, routing or appointment exception, and invoice mismatch. Each chargeback has its own code and dispute path, but they share one root cause. Fixing them as five separate events misses the pattern is like playing whack a mole. Fixing the root cause ASN process closes all five.",
|
|
209
|
+
"answerQualifier": "Based on public EDI and compliance documentation from SPS Commerce, Orderful, BOLD VAN, Inmar, and Consulterce, September 2026. Fee percentages are vendor-reported and vary by retailer and program update.",
|
|
210
|
+
"faq": [
|
|
211
|
+
{
|
|
212
|
+
"q": "Can one shipment really generate five separate chargebacks?",
|
|
213
|
+
"a": "Yes. A late or inaccurate ASN touches five different compliance categories because the 856 is the document that connects PO fulfillment, warehouse shipment, carrier appointment, retailer receiving, and invoicing. When the ASN is wrong, every system downstream records a different version of the same error, and each version gets its own chargeback code."
|
|
214
|
+
},
|
|
215
|
+
{
|
|
216
|
+
"q": "What is the most common ASN error that triggers multiple chargebacks?",
|
|
217
|
+
"a": "A carton-count change after ASN generation. The warehouse adjusts the physical shipment, but the already-transmitted 856 carries the original count. The retailer receives a quantity that doesn't match the ASN, which triggers an ASN accuracy chargeback and a shortage claim. If the pick change also delayed the shipment, an OTIF miss follows."
|
|
218
|
+
},
|
|
219
|
+
{
|
|
220
|
+
"q": "How do I know if my deductions share a single root cause?",
|
|
221
|
+
"a": "Pull five recent deductions and trace them back to the PO number. If two or more chargebacks on the same remittance point to the same PO, they likely started from one shipment failure. The evidence pack for that PO will show where the chain broke."
|
|
222
|
+
},
|
|
223
|
+
{
|
|
224
|
+
"q": "Does fixing the ASN process actually reduce chargebacks from other categories?",
|
|
225
|
+
"a": "It reduces every chargeback category that depends on the ASN being accurate and on time: shortage claims that started as a count mismatch, OTIF misses that started as a late transmission, and invoice mismatches where the 810 followed the wrong ASN quantity. BOLD VAN reports that focused remediation targeting top chargeback categories reduces chargeback volume by 50 to 80% within one to two quarters."
|
|
226
|
+
}
|
|
227
|
+
]
|
|
228
|
+
},
|
|
229
|
+
{
|
|
230
|
+
"slug": "business-central-edi-failures",
|
|
231
|
+
"title": "The Five Business Central Settings Driving Retailer Deductions",
|
|
232
|
+
"description": "Five Business Central EDI failure modes that end as retailer deductions: item references, unit of measure, posting timing, and ship-to mapping.",
|
|
233
|
+
"pubDate": "2026-08-24T00:00:00.000Z",
|
|
234
|
+
"author": "Pixels and Clicks",
|
|
235
|
+
"tags": [
|
|
236
|
+
"EDI",
|
|
237
|
+
"Business Central",
|
|
238
|
+
"Dynamics 365",
|
|
239
|
+
"ERP",
|
|
240
|
+
"ASN",
|
|
241
|
+
"856",
|
|
242
|
+
"Retail Compliance"
|
|
243
|
+
],
|
|
244
|
+
"readingTime": 8,
|
|
245
|
+
"cluster": "erp-technical",
|
|
246
|
+
"draft": false,
|
|
247
|
+
"hideToc": true,
|
|
248
|
+
"image": "/images/articles/business-central-edi-failures-banner.jpg",
|
|
249
|
+
"imageAlt": "Business Central EDI 856 ASN failures",
|
|
250
|
+
"answer": "Business Central generates no X12 EDI on its own, so every retailer ASN passes through a connector reading BC records. Five gaps corrupt it before transmission: missing item references, a wrong Qty. per Unit of Measure, a trigger wired to the wrong warehouse posting step, an unmapped ship-to or GLN, and kits that never explode to pack level.",
|
|
251
|
+
"answerQualifier": "Based on Microsoft Learn documentation for Dynamics 365 Business Central covering item references, item units of measure, outbound warehouse flow, the Ship-to Address table, and assembly items, August 2026. Business Central's own fields and behavior are documented. Which validations a given EDI connector runs before transmission varies by vendor and is not a public standard.",
|
|
252
|
+
"faq": [
|
|
253
|
+
{
|
|
254
|
+
"q": "Does Business Central handle EDI natively?",
|
|
255
|
+
"a": "No. Business Central ships with a Data Exchange Framework and support for PEPPOL electronic invoices, which is a European e-invoicing standard, not retail X12. For a Walmart or Target ASN you need a connector or middleware layer that reads Business Central records and translates them into X12. That translation layer is where most retail EDI configuration actually lives."
|
|
256
|
+
},
|
|
257
|
+
{
|
|
258
|
+
"q": "Why does a unit-of-measure setting cause a shortage deduction?",
|
|
259
|
+
"a": "The Qty. per Unit of Measure field on an item's alternate unit tells Business Central how many base units a case contains. If your ASN declares eaches where the retailer's implementation guide expects cases, your reported quantity is off by exactly the case-pack multiplier. The receiving count then reads short or over, and a short read becomes a shortage deduction."
|
|
260
|
+
},
|
|
261
|
+
{
|
|
262
|
+
"q": "When should the ASN transmit relative to Business Central's warehouse posting?",
|
|
263
|
+
"a": "After the pick is registered and the shipment is posted, not before. In an advanced warehouse configuration, a registered warehouse pick updates Qty. Picked but does not post the shipment, so an ASN fired at pick registration describes intended quantities rather than confirmed ones. Posting the warehouse shipment is the event that reflects what actually left."
|
|
264
|
+
},
|
|
265
|
+
{
|
|
266
|
+
"q": "What is the GLN field on a Business Central ship-to address for?",
|
|
267
|
+
"a": "GLN is the Global Location Number, a 13-character GS1 identifier for a physical location. Retailers use it to identify the receiving DC on EDI documents. Business Central has a dedicated GLN field on the Ship-to Address table, and leaving it blank forces your connector to derive the DC identity some other way, usually from a mapping table maintained by hand and updated late when a retailer opens a new facility."
|
|
268
|
+
},
|
|
269
|
+
{
|
|
270
|
+
"q": "Do I need to replace Business Central to fix these?",
|
|
271
|
+
"a": "No. All five gaps are configuration and validation problems inside records Business Central already has: the item card, item references, item units of measure, the ship-to address, and the assembly BOM. The work is deciding which check runs before transmission and where it runs, not changing systems."
|
|
272
|
+
}
|
|
273
|
+
]
|
|
274
|
+
},
|
|
275
|
+
{
|
|
276
|
+
"slug": "cpg-cash-gap-walmart-dependency-data",
|
|
277
|
+
"title": "Smaller CPG Brands Fund a 68-Day Cash Gap. Two Free Tools Show Yours.",
|
|
278
|
+
"description": "Brands under $10B carry a 68-day cash gap. The largest CPG companies carry none. Two free SEC-data tools measure yours.",
|
|
279
|
+
"pubDate": "2026-10-19T00:00:00.000Z",
|
|
280
|
+
"author": "Pixels and Clicks",
|
|
281
|
+
"tags": [
|
|
282
|
+
"Working Capital",
|
|
283
|
+
"Cash Conversion Cycle",
|
|
284
|
+
"Walmart",
|
|
285
|
+
"Supplier Finance",
|
|
286
|
+
"Customer Concentration",
|
|
287
|
+
"Research"
|
|
288
|
+
],
|
|
289
|
+
"readingTime": 7,
|
|
290
|
+
"cluster": "scoping",
|
|
291
|
+
"hub": "deduction-management-for-cpg-suppliers",
|
|
292
|
+
"draft": false,
|
|
293
|
+
"hideToc": true,
|
|
294
|
+
"image": "/images/articles/cpg-cash-gap-walmart-dependency-data-banner.jpg",
|
|
295
|
+
"imageAlt": "Hand-drawn whiteboard diagram of cash flowing from retailers to large CPG brands to smaller brands",
|
|
296
|
+
"answer": "The median CPG company over $10B in revenue has a cash conversion cycle of about -3 days, so it collects before it pays suppliers. The median public CPG company under $10B carries a 68-day gap, per Pixels and Clicks analysis of SEC 10-K filings. Two free tools measure your own gap and customer concentration.",
|
|
297
|
+
"answerQualifier": "Based on Pixels and Clicks analysis of 10-K filings from 19 retailers and 58 CPG manufacturers, October 2026.",
|
|
298
|
+
"faq": [
|
|
299
|
+
{
|
|
300
|
+
"q": "What is the cash conversion cycle for CPG companies?",
|
|
301
|
+
"a": "The cash conversion cycle is days to collect from customers, plus days of inventory, minus days payable. In 10-K filings analyzed by Pixels and Clicks, the median CPG company over $10B in revenue runs about -3 days. The median public CPG company under $10B runs 68 days. That company funds more than two months of its own working capital."
|
|
302
|
+
},
|
|
303
|
+
{
|
|
304
|
+
"q": "Does Walmart owe its suppliers more than its inventory is worth?",
|
|
305
|
+
"a": "Yes, on its balance sheet. At the end of January 2026, Walmart reported $63.1B in accounts payable and $58.9B in inventory. Payables equaled 107% of inventory, up from 84% in January 2009. Accounts payable covers all of Walmart's vendors, not only CPG brands."
|
|
306
|
+
},
|
|
307
|
+
{
|
|
308
|
+
"q": "How dependent are CPG companies on Walmart?",
|
|
309
|
+
"a": "Pixels and Clicks found 22 public CPG companies that reported Walmart's share of their sales in both 2009 and 2024. Of those, 14 now depend on Walmart more. Their median Walmart share rose from 18.5% to 22%. John B. Sanfilippo reported the largest rise, from 19% of net sales in fiscal 2009 to 41% in fiscal 2026."
|
|
310
|
+
},
|
|
311
|
+
{
|
|
312
|
+
"q": "Is days payable the same as payment terms?",
|
|
313
|
+
"a": "No. Days payable is a balance-sheet ratio: accounts payable divided by cost of sales, times 365. It shows how long a company holds its bills on average. Payment terms are what a buyer and supplier agree in a contract. The two move together but are not the same number."
|
|
314
|
+
},
|
|
315
|
+
{
|
|
316
|
+
"q": "Where can I download the data?",
|
|
317
|
+
"a": "Both datasets are free to download as CSV files from The Float and the Walmart Dependency Tracker on pixelsandclicks.net. Every figure links to the 10-K filing it comes from. You can use the charts and data in your own work with a link back."
|
|
318
|
+
},
|
|
319
|
+
{
|
|
320
|
+
"q": "Can I download charts from the research pages?",
|
|
321
|
+
"a": "Yes. Every chart on The Float and the Walmart Dependency Tracker has a PNG download button. Hover over any chart figure to reveal it. The exported image is 2x resolution with a white background, ready for slides or reports."
|
|
322
|
+
},
|
|
323
|
+
{
|
|
324
|
+
"q": "Can I link to a specific section of a research page?",
|
|
325
|
+
"a": "Yes. Hover over any section heading to reveal a # link. Click it to copy a direct URL to that section. The recipient lands on that heading."
|
|
326
|
+
},
|
|
327
|
+
{
|
|
328
|
+
"q": "Can I share my Deduction Census benchmark results?",
|
|
329
|
+
"a": "Yes. After entering your numbers in the benchmark calculator, click 'Copy link to this result.' The URL encodes your deduction rate, disputed share, win rate, revenue, size band, and retailer. Anyone who opens that link sees the same comparison."
|
|
330
|
+
}
|
|
331
|
+
]
|
|
332
|
+
},
|
|
333
|
+
{
|
|
334
|
+
"slug": "data-bridge-full-cost-calculator",
|
|
335
|
+
"title": "The Real Cost of Manual Data Entry at a Mid-Market CPG",
|
|
336
|
+
"description": "Re-keying labor is the visible cost. Deductions, reconciliation hours, and rush freight stack on top. Free calculator inside.",
|
|
337
|
+
"pubDate": "2026-08-18T00:00:00.000Z",
|
|
338
|
+
"author": "Pixels and Clicks",
|
|
339
|
+
"tags": [
|
|
340
|
+
"Data Entry",
|
|
341
|
+
"EDI",
|
|
342
|
+
"ERP",
|
|
343
|
+
"Free Tools",
|
|
344
|
+
"Supply Chain Ops"
|
|
345
|
+
],
|
|
346
|
+
"readingTime": 7,
|
|
347
|
+
"cluster": "erp-technical",
|
|
348
|
+
"draft": false,
|
|
349
|
+
"hideToc": true,
|
|
350
|
+
"image": "/images/articles/data-bridge-full-cost-calculator-banner.jpg",
|
|
351
|
+
"imageAlt": "the visible labor cost of manual data entry versus the hidden cost in deductions, reconciliation, and freight",
|
|
352
|
+
"answer": "The full annual cost of manual data entry between your WMS, EDI, and ERP is more than copy pasting from one system to another. It also includes deductions from bad ASNs, hours reconciling mismatched reports, and rush freight from stale data, plus margin loss and stockout risk no report captures. In the calculator's default scenario, those three quantifiable lines roughly double the labor-only estimate.",
|
|
353
|
+
"answerQualifier": "Based on Pixels and Clicks' own manual data entry cost calculator methodology, cross-referenced with the deduction write-off pattern described in this site's EDI 856 coverage and the industry out-of-stock research cited in this site's OTIF coverage, August 2026.",
|
|
354
|
+
"faq": [
|
|
355
|
+
{
|
|
356
|
+
"q": "Why does the manual data entry cost calculator ask for deductions and freight costs, not just labor hours?",
|
|
357
|
+
"a": "Labor hours are the visible part of what manual data entry costs. The rest lands on other reports under other names: deductions traced to bad ASNs, hours spent reconciling reports that disagree, and rush freight caused by stale data. Adding those in gives the full annual cost, not just the part that shows up on a labor spreadsheet."
|
|
358
|
+
},
|
|
359
|
+
{
|
|
360
|
+
"q": "Where do I find the 'data-error incidents per month' number the calculator asks for?",
|
|
361
|
+
"a": "Your EDI portal or retailer scorecard. Count last month's rejected 824s, ASN rejections, and manual order corrections across every retailer account you run, and use that total."
|
|
362
|
+
},
|
|
363
|
+
{
|
|
364
|
+
"q": "Is the 2x multiplier in the calculator's example the same for every company?",
|
|
365
|
+
"a": "No. It's the ratio produced by the calculator's starting defaults: three coordinators, twenty incidents a month, four reconciliation hours a week. Enter your own five numbers and the ratio will move, higher for some operations, lower for others."
|
|
366
|
+
},
|
|
367
|
+
{
|
|
368
|
+
"q": "What if I don't track reconciliation hours or expedite premiums yet?",
|
|
369
|
+
"a": "Estimate them for a first pass. A rough number beats leaving the field at zero, which understates the total. The standing meeting where two systems disagree and the rush charge on a recent freight invoice are both easy to reconstruct from memory even without a formal log."
|
|
370
|
+
},
|
|
371
|
+
{
|
|
372
|
+
"q": "Does the calculator account for stockouts or lost shelf space?",
|
|
373
|
+
"a": "No, and that's on purpose. Stockout risk and buyer trust are real costs of manual data entry, but they're not consistent enough dollar figures to model in a calculator. The five inputs it does ask for are all costs you can pull from an existing report, which keeps the output defensible instead of speculative."
|
|
374
|
+
},
|
|
375
|
+
{
|
|
376
|
+
"q": "How is this different from the OTIF calculator?",
|
|
377
|
+
"a": "The OTIF calculator prices a shipment-performance gap against retailer fine schedules. The manual data entry cost calculator prices the re-entry between your systems: labor, rework, deductions, reconciliation time, and rush freight. That's what often causes the gap in the first place."
|
|
378
|
+
}
|
|
379
|
+
]
|
|
380
|
+
},
|
|
381
|
+
{
|
|
382
|
+
"slug": "deduction-dispute-deadlines-by-retailer",
|
|
383
|
+
"title": "The Deduction Dispute Windows at Walmart, Target, Amazon, Kroger",
|
|
384
|
+
"description": "Dispute windows for Walmart, Target, Amazon, and Kroger deductions in one table, with the portal and channel to file through for each.",
|
|
385
|
+
"pubDate": "2026-08-12T00:00:00.000Z",
|
|
386
|
+
"author": "Pixels and Clicks",
|
|
387
|
+
"tags": [
|
|
388
|
+
"Deductions",
|
|
389
|
+
"Dispute Deadlines",
|
|
390
|
+
"Walmart",
|
|
391
|
+
"Target",
|
|
392
|
+
"Amazon",
|
|
393
|
+
"Kroger",
|
|
394
|
+
"APDP",
|
|
395
|
+
"Synergy",
|
|
396
|
+
"Vendor Central",
|
|
397
|
+
"Lavante"
|
|
398
|
+
],
|
|
399
|
+
"readingTime": 9,
|
|
400
|
+
"cluster": "prevention",
|
|
401
|
+
"draft": false,
|
|
402
|
+
"hideToc": true,
|
|
403
|
+
"image": "/images/articles/deduction-dispute-deadlines-by-retailer-banner.jpg",
|
|
404
|
+
"imageAlt": "Hand-drawn whiteboard-style reference table with four retailer columns labeled Walmart, Target, Amazon, and Kroger, each with a clock icon showing a different dispute deadline window, a stick figure holding a calendar with question marks, and a bold hand-lettered headline reading Dispute Deadlines",
|
|
405
|
+
"answer": "Walmart gives up to two years to dispute most AP deductions through APDP, with shorter windows for chargebacks and shortages. Target allows 18 months prepaid and 9 months collect, through Synergy. Amazon chargebacks must be disputed within 30 days. Kroger gives 180 days through Supplier Connect, and reportedly 60 on an MCB fee.",
|
|
406
|
+
"answerQualifier": "Compiled from six independent vendor sources (SPS Commerce/SupplierWiki, iNymbus, Glimpse, Confido, Adbrew, Consulterce), cross-referenced against each other, August 2026.",
|
|
407
|
+
"faq": [
|
|
408
|
+
{
|
|
409
|
+
"q": "How long do I have to dispute a Walmart deduction?",
|
|
410
|
+
"a": "It depends on the type. Up to two years for general AP deductions, 12 months for shortage claims, and 15 to 30 days for chargebacks, all through APDP per SPS Commerce and Glimpse. OTIF compliance chargebacks route through HighRadius instead, with a window closer to 30 days."
|
|
411
|
+
},
|
|
412
|
+
{
|
|
413
|
+
"q": "What is Target's dispute deadline for shortages?",
|
|
414
|
+
"a": "Target's AP deduction window is 18 months from the document date on the check remittance for prepaid shipments. Collect shipments get 9 months from the shipping date, per SPS Commerce and iNymbus. Disputes go through Synergy, and a case returned as awaiting documentation auto-denies after 5 business days without a response."
|
|
415
|
+
},
|
|
416
|
+
{
|
|
417
|
+
"q": "Can I dispute an Amazon chargeback more than once?",
|
|
418
|
+
"a": "Some chargeback types allow a second dispute after the first rejection, per Adbrew and Consulterce. The initial dispute must be filed within 30 days of the chargeback notification in Vendor Central. Sources differ on whether there is a hard cap on attempts."
|
|
419
|
+
},
|
|
420
|
+
{
|
|
421
|
+
"q": "Where do I file a Kroger deduction dispute?",
|
|
422
|
+
"a": "You file through Supplier Connect, the PRGX-built platform that replaced the Lavante portal in late 2025, per iNymbus. The standard window is 180 days from the deduction date, per SPS Commerce and Confido. An MCB compliance fee is the exception, reportedly allowing 60 days and filing through the Kroger Supplier Hub instead. Once submitted, changes are not allowed, so documentation should be complete before filing."
|
|
423
|
+
},
|
|
424
|
+
{
|
|
425
|
+
"q": "Do these deadlines ever change?",
|
|
426
|
+
"a": "Yes. Retailers update programs, rename portals, and adjust windows. This table was last reviewed in August 2026 and will be updated as sources report changes. If a deadline listed here does not match what you see in your own portal, let us know so we can correct it."
|
|
427
|
+
}
|
|
428
|
+
]
|
|
429
|
+
},
|
|
430
|
+
{
|
|
431
|
+
"slug": "deduction-management-for-cpg-suppliers",
|
|
432
|
+
"title": "Deduction Management for CPG Suppliers: Stop the Leak at the Source",
|
|
433
|
+
"description": "Deduction management is how CPG suppliers track, dispute, and prevent retail chargebacks. The codes, the dispute clock, and the root-cause fix that stops them from recurring.",
|
|
434
|
+
"pubDate": "2026-11-07T00:00:00.000Z",
|
|
435
|
+
"author": "Pixels and Clicks",
|
|
436
|
+
"tags": [
|
|
437
|
+
"Deduction Management",
|
|
438
|
+
"Retail Chargebacks",
|
|
439
|
+
"Deductions",
|
|
440
|
+
"CPG",
|
|
441
|
+
"Supply Chain"
|
|
442
|
+
],
|
|
443
|
+
"readingTime": 4,
|
|
444
|
+
"cluster": "recovery",
|
|
445
|
+
"draft": false,
|
|
446
|
+
"hideToc": true,
|
|
447
|
+
"pillarOrder": 2,
|
|
448
|
+
"pillarLabel": "Deduction Management",
|
|
449
|
+
"pillarBlurb": "The end-to-end system for tracking, disputing, and preventing retail deductions.",
|
|
450
|
+
"image": "/images/articles/deduction-management-banner.jpg",
|
|
451
|
+
"imageAlt": "Hand-drawn whiteboard diagram of the deduction lifecycle: a coded remittance line decoded, validated, disputed with evidence, and the root cause fixed upstream",
|
|
452
|
+
"answer": "Deduction management is the process a CPG supplier uses to track, validate, dispute, and prevent the chargebacks and shortages retailers pull off their payments. It covers decoding each remittance line, gathering shipment evidence, filing disputes before the deadline, and fixing the root cause in the ERP or EDI setup so the same deduction stops recurring.",
|
|
453
|
+
"answerQualifier": "Based on retailer deduction and dispute processes documented across this site's Walmart, Target, Amazon, and Kroger coverage, November 2026. Programs and dispute windows change; confirm current terms in your own vendor portal.",
|
|
454
|
+
"faq": [
|
|
455
|
+
{
|
|
456
|
+
"q": "What is deduction management?",
|
|
457
|
+
"a": "Deduction management is how a supplier handles the chargebacks, shortages, and compliance fines a retailer deducts from its payments. It runs across four stages: decode the coded remittance line, validate whether the charge is real, dispute the invalid ones with evidence before the deadline, and fix the root cause so the deduction does not recur. Done well, it is a prevention discipline, not just a recovery chase."
|
|
458
|
+
},
|
|
459
|
+
{
|
|
460
|
+
"q": "What are chargebacks in retail?",
|
|
461
|
+
"a": "A retail chargeback is a deduction a retailer takes off a supplier's payment for a shipment or document that broke a rule: a late delivery, a short count, a bad label, or a mismatched EDI file. It posts as a coded line on the remittance weeks after delivery and is separate from a product return. Each retailer uses its own code set and dispute portal."
|
|
462
|
+
},
|
|
463
|
+
{
|
|
464
|
+
"q": "Is deduction management software or a service better?",
|
|
465
|
+
"a": "Software automates tracking and dispute filing, which helps at high volume, but most tools stop at recovery: chasing deductions after they post. For a mid-market CPG supplier the larger win is root cause, closing the ERP and EDI gaps that generate the charge in the first place. That is a service and process question, not only a software one, so the two are complements rather than substitutes."
|
|
466
|
+
},
|
|
467
|
+
{
|
|
468
|
+
"q": "How do you reduce retail deductions?",
|
|
469
|
+
"a": "Start by separating the pattern from the noise: which code, at which retailer, from which cause. Validate before you pay, because a share of deductions are duplicates or invalid. Dispute the recoverable ones inside the window. Then fix the upstream data or document gap, since many deductions trace to an ASN, invoice, or unit-of-measure mismatch rather than a warehouse failure."
|
|
470
|
+
},
|
|
471
|
+
{
|
|
472
|
+
"q": "How long do you have to dispute a deduction?",
|
|
473
|
+
"a": "The clock is set per retailer and it is unforgiving. Walmart disputes run through APDP in Retail Link, Amazon through Vendor Central, and Target and Kroger through their own portals, each with a different window. Miss the deadline and a preventable, disputable charge becomes permanent, so the dispute clock usually matters more than the merits of the case."
|
|
474
|
+
}
|
|
475
|
+
]
|
|
476
|
+
},
|
|
477
|
+
{
|
|
478
|
+
"slug": "demand-forecasting-data-readiness",
|
|
479
|
+
"title": "Is Your Data Ready for Netstock, o9, or Blue Yonder?",
|
|
480
|
+
"description": "The six data-readiness checks that decide whether a Netstock, o9, or Blue Yonder pilot ships a working forecast at your SKU catalog.",
|
|
481
|
+
"pubDate": "2026-08-18T00:00:00.000Z",
|
|
482
|
+
"author": "Pixels and Clicks",
|
|
483
|
+
"tags": [
|
|
484
|
+
"Demand Forecasting",
|
|
485
|
+
"S&OP",
|
|
486
|
+
"Data Readiness",
|
|
487
|
+
"MAPE",
|
|
488
|
+
"CPG",
|
|
489
|
+
"Inventory Planning"
|
|
490
|
+
],
|
|
491
|
+
"readingTime": 8,
|
|
492
|
+
"cluster": "forecasting",
|
|
493
|
+
"hub": "supplier-scorecard-for-cpg-suppliers",
|
|
494
|
+
"draft": false,
|
|
495
|
+
"hideToc": true,
|
|
496
|
+
"image": "/images/articles/demand-forecasting-data-readiness-banner.jpg",
|
|
497
|
+
"imageAlt": "what demand forecasting for CPG requires",
|
|
498
|
+
"answer": "CPG demand-forecasting data readiness means your SKU history, unit-of-measure consistency, promotional flagging, and master-data hygiene can support a statistical model before you buy one. A platform can run a technically correct forecast on messy inputs and still produce numbers you shouldn't order against. The six checks: history depth, UOM consistency, promo/baseline separation, master-data change control, stockout-vs-zero-demand distinction, and accuracy tracking.",
|
|
499
|
+
"answerQualifier": "Based on Oracle NetSuite's demand-planning documentation, the Institute of Business Forecasting's MAPE reference, and CPG-specific trade-promotion forecasting guidance (Vividly), August 2026.",
|
|
500
|
+
"faq": [
|
|
501
|
+
{
|
|
502
|
+
"q": "How many years of sales history does a demand-forecasting platform need?",
|
|
503
|
+
"a": "There's no universal number, and Oracle's own NetSuite demand-planning documentation doesn't state a minimum. What matters is continuity: enough clean periods to separate a real trend or seasonal pattern from ordinary noise. A seasonal category typically needs at least two full cycles to tell the two apart. Less than a year, or a year full of gaps, is the tier our own readiness quiz scores as not ready."
|
|
504
|
+
},
|
|
505
|
+
{
|
|
506
|
+
"q": "What is MAPE, and what counts as a good score?",
|
|
507
|
+
"a": "MAPE (Mean Absolute Percentage Error) averages the absolute percentage gap between what you forecast and what actually sold. There's no universal \"good\" threshold; it depends on category, volatility, and horizon length. What matters more than the number itself is whether you're tracking it consistently enough to know if it's improving."
|
|
508
|
+
},
|
|
509
|
+
{
|
|
510
|
+
"q": "Can I run a forecasting platform if my promotional and base demand aren't separated yet?",
|
|
511
|
+
"a": "You can run it, but expect the forecast to be wrong in a predictable direction. A quarter with a major promotion inflates what the model treats as your steady-state baseline, so the next quarter's forecast inherits demand that isn't there, and you over-buy against it. Separate the two before go-live if you can; if you can't, treat the first two quarters of forecasts as suspect."
|
|
512
|
+
},
|
|
513
|
+
{
|
|
514
|
+
"q": "What's the difference between a stockout and real zero demand in forecasting data?",
|
|
515
|
+
"a": "A stockout is demand that existed and went unmet; a zero-demand period is demand that genuinely wasn't there. Sales history records both as the same zero. A model that can't tell them apart learns that an item sells less than it does, and forecasts accordingly, training itself cycle after cycle to keep you understocked on exactly the items that stocked out before."
|
|
516
|
+
}
|
|
517
|
+
]
|
|
518
|
+
},
|
|
519
|
+
{
|
|
520
|
+
"slug": "edi-810-invoice-mismatch-deductions",
|
|
521
|
+
"title": "EDI 810: How One Pack-Size Field Becomes a Shortage Deduction",
|
|
522
|
+
"description": "One pack-size mismatch in your item file, carried through the 850, 856, and 810, becomes a shortage deduction for goods that actually arrived.",
|
|
523
|
+
"pubDate": "2026-08-27T00:00:00.000Z",
|
|
524
|
+
"author": "Pixels and Clicks",
|
|
525
|
+
"tags": [
|
|
526
|
+
"EDI",
|
|
527
|
+
"810",
|
|
528
|
+
"Invoice",
|
|
529
|
+
"Shortage",
|
|
530
|
+
"Three-Way Match",
|
|
531
|
+
"ERP",
|
|
532
|
+
"Retail Compliance"
|
|
533
|
+
],
|
|
534
|
+
"readingTime": 8,
|
|
535
|
+
"cluster": "erp-technical",
|
|
536
|
+
"draft": false,
|
|
537
|
+
"hideToc": true,
|
|
538
|
+
"image": "/images/articles/edi-810-invoice-mismatch-deductions-banner.jpg",
|
|
539
|
+
"imageAlt": "EDI 810 invoice document chain: 850 to 856 to 810 three-way match producing a shortage deduction",
|
|
540
|
+
"answer": "The retailer's AP department compares three records before releasing payment: the 850 purchase order, the receiving scan (staged by the 856 ASN), and the 810 invoice. When the quantities across those three disagree, the system records a shortage, not a data error. Most shortage deductions trace to a stale item-file field, a wrong unit of measure or an outdated case-pack count, that traveled through every document unchallenged until the receiving scan disagreed with the invoice.",
|
|
541
|
+
"answerQualifier": "Based on the public X12 810 transaction-set structure (Stedi, BOLD VAN, Celigo, SignalEDI documentation), SPS Commerce shortage-cause references, and Microsoft Learn three-way-match documentation, August 2026. Segment names are the public standard; individual retailer tolerance rules and match thresholds vary.",
|
|
542
|
+
"faq": [
|
|
543
|
+
{
|
|
544
|
+
"q": "What is an EDI 810?",
|
|
545
|
+
"a": "The EDI 810 is the electronic invoice a supplier transmits after shipping. It carries the invoice number, PO reference, line-item quantities, unit prices, and the total amount due. The retailer's AP department compares it against the original purchase order (850) and the advance ship notice (856) before releasing payment."
|
|
546
|
+
},
|
|
547
|
+
{
|
|
548
|
+
"q": "Why did I get a shortage deduction when everything shipped?",
|
|
549
|
+
"a": "The retailer's three-way match compares what you invoiced against what their receiving scan recorded, not against what physically arrived. If your 810 bills 120 eaches and their system expected 10 cases of 12, the match fails even though the same goods are on the dock. The mismatch is in the data, not the warehouse."
|
|
550
|
+
},
|
|
551
|
+
{
|
|
552
|
+
"q": "What is a three-way match in retail AP?",
|
|
553
|
+
"a": "A three-way match compares three records before paying an invoice: the purchase order (what was ordered), the receiving record (what the warehouse counted, staged by the ASN), and the invoice (what the supplier billed). Any disagreement among the three becomes a short-pay or a deduction code on the remittance."
|
|
554
|
+
},
|
|
555
|
+
{
|
|
556
|
+
"q": "What's the difference between an 810 and an 856?",
|
|
557
|
+
"a": "The 856 Advance Ship Notice describes what's in a shipment before or as it moves. The 810 invoice bills for it afterward. They should describe the same quantities, and when they don't, that gap is where most shortage-code deductions originate. For the full 856 breakdown, see [EDI 856 (ASN): why retailers reject it](/articles/edi-856-asn-rejections.html)."
|
|
558
|
+
},
|
|
559
|
+
{
|
|
560
|
+
"q": "Can I dispute an invoice-adjustment deduction?",
|
|
561
|
+
"a": "Usually yes, if you have the evidence: a signed bill of lading or proof of delivery showing the correct quantity, the original PO, and the ASN. The dispute window varies by retailer. See the [dispute-deadline reference table](/articles/deduction-dispute-deadlines-by-retailer.html) for reported timelines."
|
|
562
|
+
}
|
|
563
|
+
]
|
|
564
|
+
},
|
|
565
|
+
{
|
|
566
|
+
"slug": "edi-824-rejection-codes",
|
|
567
|
+
"title": "EDI 824: How to Read the Rejection Codes",
|
|
568
|
+
"description": "The EDI 824 tells you why a transmission failed, not just whether it arrived. How OTI and TED segments work, and why an unresolved 824 becomes a deduction.",
|
|
569
|
+
"pubDate": "2026-08-04T00:00:00.000Z",
|
|
570
|
+
"author": "Pixels and Clicks",
|
|
571
|
+
"tags": [
|
|
572
|
+
"EDI",
|
|
573
|
+
"824",
|
|
574
|
+
"Application Advice",
|
|
575
|
+
"ERP",
|
|
576
|
+
"Retail Compliance"
|
|
577
|
+
],
|
|
578
|
+
"readingTime": 7,
|
|
579
|
+
"cluster": "erp-technical",
|
|
580
|
+
"draft": false,
|
|
581
|
+
"hideToc": true,
|
|
582
|
+
"image": "/images/articles/edi-824-rejection-codes-banner.jpg",
|
|
583
|
+
"imageAlt": "Hand-drawn whiteboard-style diagram explaining the EDI 824 Application Advice: a document flowing through an OTI segment check and a TED error-code segment, labeled with arrows, showing how an unresolved rejection turns into a deduction weeks later",
|
|
584
|
+
"answer": "The EDI 824 Application Advice tells a trading partner why a document's content, not its syntax, failed: a duplicate invoice, an out-of-balance total, a missing reference. It arrives after a clean 997 confirms only that the transmission was structurally valid. An unresolved 824 rejection routinely becomes a deduction on the remittance weeks later, with nothing connecting the two.",
|
|
585
|
+
"answerQualifier": "Based on the public X12 824 transaction-set structure (Stedi's EDI reference), Kroger's public EDI portal error-code documentation, and LearnEDI.org's 824 reference, August 2026. Segment names and the OTI/TED structure are the public standard; individual retailers layer their own longer error-code catalogs on top.",
|
|
586
|
+
"faq": [
|
|
587
|
+
{
|
|
588
|
+
"q": "What's the difference between a 997 and an 824?",
|
|
589
|
+
"a": "The 997 Functional Acknowledgment confirms a transmission arrived and parsed as valid EDI syntax, nothing about whether the business content makes sense. The 824 Application Advice is what tells you the content itself was rejected or flagged: a duplicate invoice, a total that doesn't balance, a reference the retailer's system doesn't recognize. For the full side-by-side comparison, see [EDI 997 vs. 824](https://www.pixelsandclicks.net/articles/edi-997-vs-824.html)."
|
|
590
|
+
},
|
|
591
|
+
{
|
|
592
|
+
"q": "Is an 824 rejection the same as a chargeback?",
|
|
593
|
+
"a": "Not directly. The 824 is a data-validation response, not a deduction. But an 824 you don't act on routinely becomes one. If the underlying document (an invoice or ASN) never gets corrected and resent, the mismatch it flagged shows up as a shortage or pricing deduction on a later remittance."
|
|
594
|
+
},
|
|
595
|
+
{
|
|
596
|
+
"q": "Do all retailers send 824s?",
|
|
597
|
+
"a": "No. Some retailers validate content and simply deduct silently if something doesn't match, with no 824 program at all. Where an 824 program exists, it's the closest thing to a free early-warning system a supplier gets before a deduction shows up."
|
|
598
|
+
},
|
|
599
|
+
{
|
|
600
|
+
"q": "What does TED01 mean on an 824?",
|
|
601
|
+
"a": "TED01 is the numeric error condition code inside the Technical Error Description segment. It's a small, generic list, things like 006 (Duplicate) or 007 (Missing Data). Read it together with TED02, the free-text field where the retailer explains what specifically triggered it."
|
|
602
|
+
}
|
|
603
|
+
]
|
|
604
|
+
},
|
|
605
|
+
{
|
|
606
|
+
"slug": "edi-856-asn-rejections",
|
|
607
|
+
"title": "EDI 856 (ASN): Why Retailers Reject It",
|
|
608
|
+
"description": "What the EDI 856 Advance Ship Notice carries, the six most common reasons retailers reject it, and which deduction it becomes if you don't catch it.",
|
|
609
|
+
"pubDate": "2026-08-02T00:00:00.000Z",
|
|
610
|
+
"author": "Pixels and Clicks",
|
|
611
|
+
"tags": [
|
|
612
|
+
"EDI",
|
|
613
|
+
"ASN",
|
|
614
|
+
"856",
|
|
615
|
+
"ERP",
|
|
616
|
+
"Retail Compliance"
|
|
617
|
+
],
|
|
618
|
+
"readingTime": 7,
|
|
619
|
+
"cluster": "erp-technical",
|
|
620
|
+
"draft": false,
|
|
621
|
+
"hideToc": true,
|
|
622
|
+
"image": "/images/articles/edi-856-asn-rejections-banner.jpg",
|
|
623
|
+
"imageAlt": "Hand-drawn whiteboard-style diagram explaining the EDI 856 Advance Ship Notice: a truck and a shipment carton labeled with carton counts, SSCC labels, and item quantities, with an arrow showing a rejected ASN turning into a shortage deduction",
|
|
624
|
+
"answer": "The EDI 856 Advance Ship Notice tells a retailer what's in a shipment before it physically arrives: carton counts, SSCC labels, and item quantities in a hierarchical structure. When it's late, mismatched, or structurally wrong, the retailer's system doesn't record a data error. It records a shortage or a chargeback that shows up weeks later on a remittance.",
|
|
625
|
+
"answerQualifier": "Based on the public X12 856 transaction-set structure (Stedi's EDI reference, SupplyPike/SPS Commerce documentation), August 2026. Segment names and hierarchy are the public standard; individual retailer implementation guides vary in which segments are required.",
|
|
626
|
+
"faq": [
|
|
627
|
+
{
|
|
628
|
+
"q": "What happens if an 856 is rejected?",
|
|
629
|
+
"a": "Depends on the retailer's system. Some reject the transmission outright and send back a 997 or 824 flagging the error, which you can fix and resend before the truck arrives. But a clean 997 by itself only confirms the file parsed, not that the content was accepted (see [EDI 997 vs. 824](https://www.pixelsandclicks.net/articles/edi-997-vs-824.html)). Others accept a structurally valid but inaccurate 856, and the mismatch surfaces later as a receiving discrepancy: no error message, just a deduction weeks after the fact."
|
|
630
|
+
},
|
|
631
|
+
{
|
|
632
|
+
"q": "How late can an ASN be before it counts against you?",
|
|
633
|
+
"a": "There's no single standard window. Each retailer sets its own. Most require transmission before the shipment physically arrives, not before it leaves your dock."
|
|
634
|
+
},
|
|
635
|
+
{
|
|
636
|
+
"q": "Does a rejected 856 always mean a deduction?",
|
|
637
|
+
"a": "No, but it removes your best evidence. The ASN is the record of what you say you shipped. Without it, you're arguing a shortage or pricing dispute with no proof on your side."
|
|
638
|
+
},
|
|
639
|
+
{
|
|
640
|
+
"q": "What's the difference between an 856 and an 810?",
|
|
641
|
+
"a": "The 856 is the Advance Ship Notice, sent before or as the shipment moves. The [810 is the invoice](/articles/edi-810-invoice-mismatch-deductions.html), generated afterward to bill for it. They should describe the same quantities, and when they don't, that gap is where most shortage-code deductions originate."
|
|
642
|
+
}
|
|
643
|
+
]
|
|
644
|
+
},
|
|
645
|
+
{
|
|
646
|
+
"slug": "edi-997-vs-824",
|
|
647
|
+
"title": "EDI 997 vs. 824: What Flags a Failure",
|
|
648
|
+
"description": "A clean 997 only confirms your EDI transmission parsed, not that the retailer accepted the content. What each acknowledgment actually checks.",
|
|
649
|
+
"pubDate": "2026-08-10T00:00:00.000Z",
|
|
650
|
+
"author": "Pixels and Clicks",
|
|
651
|
+
"tags": [
|
|
652
|
+
"EDI",
|
|
653
|
+
"997",
|
|
654
|
+
"824",
|
|
655
|
+
"Functional Acknowledgment",
|
|
656
|
+
"Application Advice",
|
|
657
|
+
"ERP"
|
|
658
|
+
],
|
|
659
|
+
"readingTime": 7,
|
|
660
|
+
"cluster": "erp-technical",
|
|
661
|
+
"draft": false,
|
|
662
|
+
"hideToc": true,
|
|
663
|
+
"image": "/images/articles/edi-997-vs-824-banner.jpg",
|
|
664
|
+
"imageAlt": "Hand-drawn whiteboard-style diagram comparing the EDI 997 Functional Acknowledgment and 824 Application Advice: a document passing a syntax check labeled 997, then a content check labeled 824, with a branch showing what happens when no 824 exists",
|
|
665
|
+
"answer": "The EDI 997 Functional Acknowledgment confirms only that a transmission parsed as valid syntax, not that the retailer accepted the content. The EDI 824 Application Advice reports that separately, later, and only where a retailer chooses to send one. A clean 997 with no follow-up 824 is not proof of acceptance.",
|
|
666
|
+
"answerQualifier": "Based on the public X12 997 and 824 transaction-set structure (Stedi's EDI reference), Kroger's public EDI portal documentation, and LearnEDI.org's acknowledgment references, August 2026. Segment names and the two-document structure are the public standard; which retailers run an 824 program at all is implementation-specific and not universal.",
|
|
667
|
+
"faq": [
|
|
668
|
+
{
|
|
669
|
+
"q": "What's the difference between a 997 and an 824?",
|
|
670
|
+
"a": "The 997 Functional Acknowledgment confirms a transmission arrived and parsed as valid EDI syntax, nothing about the business content. The 824 Application Advice reports whether that content was actually accepted, once the retailer's system tries to process it. That content might be an invoice total, a PO reference, or a shipment quantity. They answer different questions and neither substitutes for the other."
|
|
671
|
+
},
|
|
672
|
+
{
|
|
673
|
+
"q": "If I get a clean 997, does that mean my EDI document was accepted?",
|
|
674
|
+
"a": "No. It means the envelope was structurally valid, right segments, right order, right delimiters. Whether the retailer's system did anything useful with the content inside is a separate question. Where an 824 exists, it answers that question later. Where it doesn't, the question goes unanswered."
|
|
675
|
+
},
|
|
676
|
+
{
|
|
677
|
+
"q": "Do all retailers send an 824?",
|
|
678
|
+
"a": "No. Some retailers validate content and simply deduct against the remittance if something doesn't match, with no application-advice program at all. Where that's the case, a clean 997 is the only acknowledgment you'll ever get, and it was never designed to tell you what you're using it for."
|
|
679
|
+
},
|
|
680
|
+
{
|
|
681
|
+
"q": "Is a rejected 824 the same as a chargeback?",
|
|
682
|
+
"a": "Not directly. It's a data-validation response, not a deduction. But an 824 rejection that goes uncorrected routinely becomes one. The gap between the two is usually 30 or more days, with nothing on the remittance connecting the eventual deduction back to the written warning that preceded it."
|
|
683
|
+
},
|
|
684
|
+
{
|
|
685
|
+
"q": "What should I actually monitor if I only get 997s?",
|
|
686
|
+
"a": "Watch the receiving and payment signals downstream of the document itself, since there's no earlier warning coming. That means tracking invoice-to-payment variance, unexpected remittance deduction codes, and receiving discrepancies as the de facto acknowledgment, weeks later than an 824 would have told you."
|
|
687
|
+
}
|
|
688
|
+
]
|
|
689
|
+
},
|
|
690
|
+
{
|
|
691
|
+
"slug": "erp-says-shipped-retailer-says-short",
|
|
692
|
+
"title": "Why Your ERP Says Shipped and the Retailer Says Short",
|
|
693
|
+
"description": "Four quantities from four systems create one shortage deduction. Trace from PO to ERP to WMS to ASN to receipt, find the first mismatch, and stop guessing.",
|
|
694
|
+
"pubDate": "2026-09-15T00:00:00.000Z",
|
|
695
|
+
"author": "Pixels and Clicks",
|
|
696
|
+
"tags": [
|
|
697
|
+
"ERP",
|
|
698
|
+
"Shortage",
|
|
699
|
+
"Deductions",
|
|
700
|
+
"NetSuite",
|
|
701
|
+
"Business Central",
|
|
702
|
+
"ASN",
|
|
703
|
+
"EDI",
|
|
704
|
+
"UOM",
|
|
705
|
+
"Retail Compliance"
|
|
706
|
+
],
|
|
707
|
+
"readingTime": 9,
|
|
708
|
+
"cluster": "erp-technical",
|
|
709
|
+
"draft": false,
|
|
710
|
+
"hideToc": true,
|
|
711
|
+
"image": "/images/articles/erp-says-shipped-retailer-says-short-banner.jpg",
|
|
712
|
+
"imageAlt": "Four quantities from four systems creating one shortage deduction: PO, ERP, WMS, and retailer receipt diverging into a gap",
|
|
713
|
+
"answer": "A shortage deduction usually comes from a mismatch between four numbers: ordered quantity (from the PO), picked quantity (from the WMS), ASN quantity (from the EDI 856), and received quantity (from the retailer portal). Your ERP may show shipped because the shipment was posted. That doesn't prove the retailer received the same units, cases, or cartons. It also doesn't prove the ASN matched the physical shipment. To fix the deduction, trace one SKU through the full chain and find the first place the numbers diverge.",
|
|
714
|
+
"answerQualifier": "Based on public documentation from Oracle NetSuite (item fulfillment, units of measure), Microsoft Learn (Business Central item references, warehouse posting, units of measure), SPS Commerce (EDI chargebacks), BOLD VAN (EDI mapping failures), Endless Commerce (shortage deduction benchmarks), and Confido (deduction recovery), September 2026. Individual ERP configurations and retailer receiving rules vary.",
|
|
715
|
+
"faq": [
|
|
716
|
+
{
|
|
717
|
+
"q": "Why does my ERP say shipped when the retailer deducted for shortage?",
|
|
718
|
+
"a": "A posted shipment means the ERP transaction moved forward. It doesn't prove the truck carried that exact quantity. The gap usually comes from one of four places: a pick exception posted after order release, a 3PL edit made in a portal your ERP doesn't see, a unit-of-measure mismatch between your system and the retailer's, or an ASN that transmitted a different quantity than the physical shipment."
|
|
719
|
+
},
|
|
720
|
+
{
|
|
721
|
+
"q": "Can a unit-of-measure mismatch cause a shortage deduction even when nothing is physically missing?",
|
|
722
|
+
"a": "Yes. If your ASN declares 120 eaches and the retailer's system expected 10 cases of 12, the quantities are mathematically identical but the formats don't reconcile. The receiving count reads short. The retailer files a shortage deduction for goods that physically arrived. The fix is in your item master, not on the truck."
|
|
723
|
+
},
|
|
724
|
+
{
|
|
725
|
+
"q": "How do I find the root cause of a shortage deduction?",
|
|
726
|
+
"a": "Pick one deducted PO and trace one SKU. Pull the retailer PO, ERP sales order, pick ticket, ASN file, 997 and 824 responses, BOL, POD, retailer receiving record, invoice, and remittance line. Put the quantities in one row. The first place they diverge is your root cause."
|
|
727
|
+
},
|
|
728
|
+
{
|
|
729
|
+
"q": "Does a NetSuite or Business Central shipment posting prove in-full delivery?",
|
|
730
|
+
"a": "No. A posted shipment confirms the ERP transaction completed. It doesn't confirm the warehouse picked that exact quantity, the ASN transmitted the same number, or the retailer received it. The gap between the ERP posting and the retailer's receiving record is where most shortage deductions originate."
|
|
731
|
+
}
|
|
732
|
+
]
|
|
733
|
+
},
|
|
734
|
+
{
|
|
735
|
+
"slug": "free-cpg-supplier-tools-deduction-scorecard",
|
|
736
|
+
"title": "5 Free CPG Supplier Tools: Deduction Code Decoder, Scorecard Risk Checker, and More",
|
|
737
|
+
"description": "Five free tools for CPG suppliers: decode any deduction code, look up dispute deadlines, check scorecard risk, size annual deduction leakage, or track your scorecard with custom weights.",
|
|
738
|
+
"pubDate": "2026-11-09T00:00:00.000Z",
|
|
739
|
+
"author": "Pixels and Clicks",
|
|
740
|
+
"tags": [
|
|
741
|
+
"Free Tools",
|
|
742
|
+
"Deduction Management",
|
|
743
|
+
"Supplier Scorecard",
|
|
744
|
+
"OTIF",
|
|
745
|
+
"Deduction Code",
|
|
746
|
+
"CPG Suppliers"
|
|
747
|
+
],
|
|
748
|
+
"readingTime": 7,
|
|
749
|
+
"draft": false,
|
|
750
|
+
"hideToc": true,
|
|
751
|
+
"image": "/images/articles/free-cpg-supplier-tools-banner.jpg",
|
|
752
|
+
"imageAlt": "Hand-drawn black ink whiteboard sketch of five labeled tool boxes (Deduction Code Decoder, Dispute Lookup, Scorecard Risk Checker, Deduction Leakage Calc, Scorecard Template) around a central stick figure, with arrows converging into a box labeled FREE at pixelsandclicks.net",
|
|
753
|
+
"answer": "Five free tools are now live for CPG suppliers: a Retail Deduction Code Decoder, a Deduction Dispute Deadline Lookup, a Supplier Scorecard Risk Checker, a Deduction-Leakage Calculator, and a fillable Supplier Scorecard Template. We also updated the OTIF Calculator with Kroger's corrected 93% ORAD on-time threshold. No login, no trial, no form required for any of them.",
|
|
754
|
+
"answerQualifier": "Pixels and Clicks site update, November 2026.",
|
|
755
|
+
"faq": [
|
|
756
|
+
{
|
|
757
|
+
"q": "What is the Retail Deduction Code Decoder?",
|
|
758
|
+
"a": "A free lookup tool. Type any Walmart, Target, Amazon, or Kroger deduction code and get the retailer's label, what they're claiming, the most likely cause on the fulfillment or EDI side, and whether the deduction can be disputed and how to file. Entries sourced from vendor references rather than a retailer's own documentation are tagged Provisional."
|
|
759
|
+
},
|
|
760
|
+
{
|
|
761
|
+
"q": "What is the Deduction Dispute Deadline Lookup?",
|
|
762
|
+
"a": "A free tool where you pick a retailer and deduction type and get the dispute window, the date the clock starts (invoice date, posting date, shipping date, or notification date — it varies by retailer), the portal to file through, and any internal timers that can close a case before the published deadline. Each window carries a confidence tag based on how many sources agree."
|
|
763
|
+
},
|
|
764
|
+
{
|
|
765
|
+
"q": "What is the Supplier Scorecard Risk Checker?",
|
|
766
|
+
"a": "A free diagnostic tool that scores your on-time delivery, fill rate, and ASN accuracy against each retailer's reported thresholds and returns a composite risk score and risk band (green, amber, or red) with a per-metric breakdown. Answer 12 questions in about four minutes and get your score: no login required."
|
|
767
|
+
},
|
|
768
|
+
{
|
|
769
|
+
"q": "What does the Deduction-Leakage Calculator do?",
|
|
770
|
+
"a": "It estimates how much retail deductions reduce your annual revenue. Enter your revenue by retailer and your known deduction rate. The calculator sizes total annual leakage and splits it into recoverable (through disputes) and preventable (through ERP and EDI fixes) portions."
|
|
771
|
+
},
|
|
772
|
+
{
|
|
773
|
+
"q": "What changed in the OTIF Calculator for Kroger?",
|
|
774
|
+
"a": "The Kroger threshold was corrected to 93% under the ORAD program. ORAD stands for Order Receipt and Acknowledgement Date, the timestamp Kroger creates when it confirms your delivery booking. If you modeled Kroger fine exposure with the old version, run it again."
|
|
775
|
+
},
|
|
776
|
+
{
|
|
777
|
+
"q": "What is the Supplier Scorecard Template?",
|
|
778
|
+
"a": "A free, fillable browser tool. Set the weight for each metric (on-time delivery, fill rate, ASN accuracy, compliance), enter your actual scores, and get a weighted composite. Download as CSV to track month over month in your own spreadsheet or reporting tool."
|
|
779
|
+
}
|
|
780
|
+
]
|
|
781
|
+
},
|
|
782
|
+
{
|
|
783
|
+
"slug": "holiday-forecast-trap-otif-risk",
|
|
784
|
+
"title": "The Retailer's Peak Forecast Will Cost You OTIF in November",
|
|
785
|
+
"description": "Peak-season retailer forecasts overstate demand. Accepting one without a counter-model stacks OTIF risk in November and inventory write-downs in January.",
|
|
786
|
+
"pubDate": "2026-09-01T00:00:00.000Z",
|
|
787
|
+
"author": "Pixels and Clicks",
|
|
788
|
+
"tags": [
|
|
789
|
+
"Forecasting",
|
|
790
|
+
"OTIF",
|
|
791
|
+
"Peak Season",
|
|
792
|
+
"Walmart",
|
|
793
|
+
"Retail Compliance",
|
|
794
|
+
"Q4"
|
|
795
|
+
],
|
|
796
|
+
"readingTime": 8,
|
|
797
|
+
"cluster": "forecasting",
|
|
798
|
+
"hub": "supplier-scorecard-for-cpg-suppliers",
|
|
799
|
+
"draft": false,
|
|
800
|
+
"hideToc": true,
|
|
801
|
+
"image": "/images/articles/holiday-forecast-trap-otif-risk-banner.jpg",
|
|
802
|
+
"imageAlt": "Whiteboard-style diagram of a CPG supplier receiving an inflated Q4 forecast from a retailer, showing the branching risks of accepting it uncritically: OTIF fine in November, shortage claims in December, and markdown deductions in January",
|
|
803
|
+
"answer": "Retailer peak-season forecasts routinely overstate demand by 10 to 25 percent, and accepting one without running a supplier-side counter-forecast commits you to inventory and capacity you may not clear. The trap is not the forecast. The trap is treating it as an order commitment. Build a POS-driven counter-forecast, flag any line where the retailer number sits more than 15 percent above your own, and negotiate the delta before you cut a purchase order to your co-packer.",
|
|
804
|
+
"answerQualifier": "Based on public forecasting and retailer-compliance documentation from SPS Commerce, BOLD VAN, Endless Commerce, and Supply Chain Dive, September 2026. Retailer forecast tools and thresholds vary by program.",
|
|
805
|
+
"faq": [
|
|
806
|
+
{
|
|
807
|
+
"q": "Why do retailer peak-season forecasts overstate demand?",
|
|
808
|
+
"a": "Category buyers face asymmetric risk. An out-of-stock at peak costs them shelf space and a sales miss. An overstock at peak costs them a markdown that hits the supplier through code 10 or a return. The rational buyer forecast leans high because the downside falls on your P&L, not theirs. This shows up most in first-year holiday programs and in categories with new SKU launches."
|
|
809
|
+
},
|
|
810
|
+
{
|
|
811
|
+
"q": "What should I do when a retailer forecast is 20% above my POS trend?",
|
|
812
|
+
"a": "Send a counter-forecast referencing your own POS data, last year's sell-through at the same account, and any current velocity signal. Ask the buyer for the assumption behind the peak lift. Do not decline. Propose a stepped commitment: firm on the first half, flexible on the second, with a case-pack contingency plan. Buyers negotiate this every year. Suppliers who accept without pushing back carry the write-down alone."
|
|
813
|
+
},
|
|
814
|
+
{
|
|
815
|
+
"q": "How does an inflated peak forecast create OTIF risk?",
|
|
816
|
+
"a": "Two paths. The first: you commit inventory, freight, and DC space to the inflated line, then a mid-November PO cut leaves the balance stranded. Your OTIF drops on the next PO because you rerouted capacity to hit the peak plan. The second: the retailer holds the forecast, sell-through underperforms, and the retailer marks down or returns the excess in January. That comes back as code 10 or codes 92, 93, 94."
|
|
817
|
+
},
|
|
818
|
+
{
|
|
819
|
+
"q": "Can I dispute an OTIF fine caused by a retailer forecast miss?",
|
|
820
|
+
"a": "The OTIF fine is a program-level chargeback measured on your aggregate on-time and in-full rate, not a per-shipment dispute. A forecast miss that damaged your fill rate is not disputable as an OTIF line. You can dispute the underlying shortage codes on the specific POs, but not the scorecard math. The prevention is upstream, before the forecast becomes an order."
|
|
821
|
+
},
|
|
822
|
+
{
|
|
823
|
+
"q": "What is the cost of accepting a peak forecast without a counter-model?",
|
|
824
|
+
"a": "It varies with category and lift, but a typical outcome for a $50 million CPG supplier accepting a 20 percent inflated Q4 forecast: two to three points of OTIF drop in November, 60 to 90 days of unproductive inventory carrying cost, and a January markdown deduction of 1 to 3 percent of the affected receipts. The forecast decision in September is a working-capital decision as much as a fill-rate decision."
|
|
825
|
+
}
|
|
826
|
+
]
|
|
827
|
+
},
|
|
828
|
+
{
|
|
829
|
+
"slug": "home-depot-routing-guide-compliance",
|
|
830
|
+
"title": "The Home Depot Routing Guide Rules That Cost Suppliers Most",
|
|
831
|
+
"description": "Home Depot's rules for carrier selection, ASN timing, and labeling. What routing, BOL, and on-time violations cost suppliers at each tier.",
|
|
832
|
+
"pubDate": "2026-08-15T00:00:00.000Z",
|
|
833
|
+
"author": "Pixels and Clicks",
|
|
834
|
+
"tags": [
|
|
835
|
+
"Home Depot",
|
|
836
|
+
"Routing Guide",
|
|
837
|
+
"Supplier Compliance",
|
|
838
|
+
"TMS",
|
|
839
|
+
"ASN",
|
|
840
|
+
"Chargebacks"
|
|
841
|
+
],
|
|
842
|
+
"readingTime": 9,
|
|
843
|
+
"cluster": "prevention",
|
|
844
|
+
"draft": false,
|
|
845
|
+
"hideToc": true,
|
|
846
|
+
"image": "/images/articles/home-depot-routing-guide-compliance-banner.jpg",
|
|
847
|
+
"imageAlt": "Home Depot distribution compliance guide retailers",
|
|
848
|
+
"answer": "Home Depot's routing guide requires suppliers to book collect shipments through its assigned carriers and TMS, hit a reported 90% on-time threshold, transmit an EDI 856 ASN before the shipment reaches the DC, and label cartons to GS1-128 spec. Violations, including using the wrong carrier on an on-time shipment, post as chargebacks deducted from the next payment.",
|
|
849
|
+
"answerQualifier": "Compiled from public freight, EDI, and logistics vendor documentation (DTS One, WarehouseQuote, Productiv, SPS Commerce, Crstl, Foundational, plus one vendor blog, iNymbus, flagged inline), August 2026. No figure confirmed against Home Depot's own Supplier Hub.",
|
|
850
|
+
"faq": [
|
|
851
|
+
{
|
|
852
|
+
"q": "What is Home Depot's routing guide?",
|
|
853
|
+
"a": "It's the document and TMS ruleset, published through Home Depot's Supplier Self-Service portal, that assigns which carrier a supplier must use for a given collect shipment based on the ship method listed on the PO. It covers shipments into the continental US, Canada, and Puerto Rico, per DTS One."
|
|
854
|
+
},
|
|
855
|
+
{
|
|
856
|
+
"q": "How much is a Home Depot routing guide violation?",
|
|
857
|
+
"a": "DTS One reports a $250 penalty for using a carrier other than the one Home Depot's routing guide assigns, applied even when the shipment itself arrives on time. No second public source confirms this exact figure, so treat it as reported, not verified."
|
|
858
|
+
},
|
|
859
|
+
{
|
|
860
|
+
"q": "Do I have to use Home Depot's assigned carrier even if my own carrier is cheaper or faster?",
|
|
861
|
+
"a": "Yes, for collect shipments. Per Productiv, using any other carrier triggers a routing non-compliance deduction regardless of delivery performance. The routing guide grades carrier choice, not delivery outcome."
|
|
862
|
+
},
|
|
863
|
+
{
|
|
864
|
+
"q": "What is Home Depot's on-time delivery requirement?",
|
|
865
|
+
"a": "DTS One and WarehouseQuote both report a 90% on-time accuracy threshold. Prepaid shipments count as on time if Home Depot receives the PO by the expected delivery date; collect shipments count as on time only if the supplier marks the PO ready to ship in the TMS by 11am local time, two days before pickup."
|
|
866
|
+
},
|
|
867
|
+
{
|
|
868
|
+
"q": "How do I dispute a Home Depot compliance violation?",
|
|
869
|
+
"a": "Through the Vendor Compliance Support process inside the Supplier Hub. SPS Commerce reports the standard dispute window opens the second Wednesday of a fiscal month and closes the second Tuesday of the following month. One vendor blog, iNymbus, separately claims a $25 minimum before a chargeback is disputable at all."
|
|
870
|
+
}
|
|
871
|
+
]
|
|
872
|
+
},
|
|
873
|
+
{
|
|
874
|
+
"slug": "how-to-dispute-walmart-deductions",
|
|
875
|
+
"title": "How to Dispute a Walmart Deduction: APDP, HighRadius, and the Timer That Closes Cases Early",
|
|
876
|
+
"description": "Step-by-step guide to disputing Walmart deductions through APDP and HighRadius, with documentation requirements and the 14-day draft timer that closes valid claims before the posted deadline.",
|
|
877
|
+
"pubDate": "2026-11-11T00:00:00.000Z",
|
|
878
|
+
"author": "Pixels and Clicks",
|
|
879
|
+
"tags": [
|
|
880
|
+
"Deductions",
|
|
881
|
+
"Walmart",
|
|
882
|
+
"Dispute Process",
|
|
883
|
+
"APDP",
|
|
884
|
+
"Chargebacks",
|
|
885
|
+
"OTIF",
|
|
886
|
+
"Deduction Management"
|
|
887
|
+
],
|
|
888
|
+
"readingTime": 9,
|
|
889
|
+
"cluster": "recovery",
|
|
890
|
+
"draft": false,
|
|
891
|
+
"hideToc": true,
|
|
892
|
+
"image": "/images/articles/how-to-dispute-walmart-deductions-banner.jpg",
|
|
893
|
+
"imageAlt": "Hand-drawn black ink whiteboard with HOW TO DISPUTE WALMART DEDUCTIONS in bold uppercase at the top, a flowchart splitting a remittance notice into two paths — APDP inside Retail Link for AP deductions and HighRadius for OTIF chargebacks — with a clock labeled 14-DAY DRAFT TIMER and a documentation stack labeled SIGNED POD, BOL, INVOICE",
|
|
894
|
+
"answer": "Walmart AP deductions and shortage claims dispute through APDP inside Retail Link. OTIF compliance chargebacks go to HighRadius — a separate system outside Retail Link. APDP has a 14-day internal draft timer: a case you open but don't submit within 14 days auto-closes without warning. The posted windows are 2 years for general AP deductions, 12 months for shortage claims, and 15 to 30 days for compliance chargebacks. Filing in the wrong portal, or leaving a case as a draft, is how valid disputes expire before the posted deadline.",
|
|
895
|
+
"answerQualifier": "Portal and window data from SPS Commerce, Glimpse, and Confido, cross-referenced August 2026. Walmart adjusts programs through Retail Link without public announcements; confirm windows in your own portal before filing.",
|
|
896
|
+
"faq": [
|
|
897
|
+
{
|
|
898
|
+
"q": "What is APDP and where do I find it?",
|
|
899
|
+
"a": "APDP stands for Accounts Payable Deduction Portal. It's Walmart's primary dispute filing system, accessible from inside Retail Link. Most deduction types — AP deductions, shortage claims, billing errors, routing chargebacks — route through APDP. OTIF compliance chargebacks are the exception and go to HighRadius instead."
|
|
900
|
+
},
|
|
901
|
+
{
|
|
902
|
+
"q": "How do I know if a Walmart deduction goes to APDP or HighRadius?",
|
|
903
|
+
"a": "OTIF compliance chargebacks route to HighRadius. All other deduction types — shortages, AP deductions, invoice errors, routing chargebacks — go to APDP. Filing an OTIF chargeback in APDP results in rejection without review. The HighRadius window is 30 days from the chargeback notice. Use the Deduction Code Decoder to confirm which portal your code uses before you open a case."
|
|
904
|
+
},
|
|
905
|
+
{
|
|
906
|
+
"q": "What is the 14-day draft timer in APDP?",
|
|
907
|
+
"a": "When you open a dispute case in APDP, it saves as a draft. If you don't submit the draft within 14 days, the case auto-closes. APDP doesn't send a warning before it closes. The draft timer runs from when you first open the case, not from when you attach documents or think you've hit submit. This timer is separate from the posted dispute window and can expire a valid claim weeks before the published deadline."
|
|
908
|
+
},
|
|
909
|
+
{
|
|
910
|
+
"q": "What documentation does Walmart require for a shortage claim?",
|
|
911
|
+
"a": "At minimum: a signed proof of delivery, bill of lading, carrier confirmation of delivery, and the original invoice. For a quantity shortage, packing slips showing what physically shipped also help. Walmart can deny a shortage dispute if the POD isn't signed by a receiver at the DC. Gather the full package before you open the case in APDP — the 14-day draft timer starts the moment you open it."
|
|
912
|
+
},
|
|
913
|
+
{
|
|
914
|
+
"q": "How long does it take Walmart to resolve a dispute?",
|
|
915
|
+
"a": "AP deduction disputes through APDP take 60 to 90 days on average. Shortage claims run longer if Walmart opens an internal receiving investigation. HighRadius OTIF disputes typically resolve faster but within the tight 30-day window. APDP shows status codes — Pending, Under Review, Additional Documentation Requested — but doesn't estimate a resolution date."
|
|
916
|
+
},
|
|
917
|
+
{
|
|
918
|
+
"q": "Can I reopen a closed APDP dispute?",
|
|
919
|
+
"a": "No. A case that closes — either because the 14-day draft timer expired or because Walmart denied it — can't be reopened through APDP. Some suppliers escalate through their Walmart buyer or category manager. The cleaner path is submitting complete documentation before the internal timer expires."
|
|
920
|
+
}
|
|
921
|
+
]
|
|
922
|
+
},
|
|
923
|
+
{
|
|
924
|
+
"slug": "kroger-supplier-deductions-guide",
|
|
925
|
+
"title": "Kroger Deduction Codes 2-9 and the 180-Day Dispute Clock",
|
|
926
|
+
"description": "Kroger deduction codes 2 through 9, the ORAD and MCB compliance fees, and the Supplier Connect dispute path. 180 days to file, 60 on MCB.",
|
|
927
|
+
"pubDate": "2026-08-25T00:00:00.000Z",
|
|
928
|
+
"author": "Pixels and Clicks",
|
|
929
|
+
"tags": [
|
|
930
|
+
"Kroger",
|
|
931
|
+
"Vendor Compliance",
|
|
932
|
+
"Deductions",
|
|
933
|
+
"Chargebacks",
|
|
934
|
+
"Lavante",
|
|
935
|
+
"Supplier Connect",
|
|
936
|
+
"ORAD",
|
|
937
|
+
"Deduction Codes"
|
|
938
|
+
],
|
|
939
|
+
"readingTime": 7,
|
|
940
|
+
"cluster": "prevention",
|
|
941
|
+
"draft": false,
|
|
942
|
+
"hideToc": true,
|
|
943
|
+
"image": "/images/articles/kroger-supplier-deductions-guide-banner.jpg",
|
|
944
|
+
"imageAlt": "Hand-drawn whiteboard-style diagram showing a Kroger remittance line with a numeric deduction code circled, an arrow pointing to a stack of vendor-source PDFs labeled SPS Commerce, iNymbus, and Confido, and a second arrow pointing to a portal window labeled Supplier Connect (formerly Lavante), with a stick figure holding a magnifying glass and a bold hand-lettered headline reading Kroger Deductions",
|
|
945
|
+
"answer": "Kroger bills suppliers on two tracks. AP codes 2 through 9 cover shortages, cost differences, and promotional allowances, with 180 days to dispute. Compliance fees like ORAD and MCB post as AR deductions instead, and an MCB fee reportedly allows only 60 days. Disputes file through Supplier Connect, which replaced Lavante in late 2025.",
|
|
946
|
+
"answerQualifier": "Compiled from six independent public vendor sources (SPS Commerce, iNymbus, Confido, WarehouseQuote, ClearChain, SupplierWiki/SupplyPike), August 2026. Kroger does not publish this itself, so every figure here is vendor-reported and flagged where sources disagree. Confirm the code and window on your own Supplier Connect remittance detail.",
|
|
947
|
+
"faq": [
|
|
948
|
+
{
|
|
949
|
+
"q": "What deduction codes does Kroger use on a remittance?",
|
|
950
|
+
"a": "Vendor sources describe eight primary AP codes (2 through 9) covering promotional allowance differences, cost mismatches, shortages, EDI non-compliance, unit shortages, overages, net-dollar catch-alls, and pickup allowances. Letter codes like SH (shortage), LC (list cost), and SD (shorted deals) appear alongside the numeric list. Compliance fees like ORAD (late delivery) and MCB (merchandising) post separately as AR deductions, not AP."
|
|
951
|
+
},
|
|
952
|
+
{
|
|
953
|
+
"q": "How long do I have to dispute a Kroger deduction?",
|
|
954
|
+
"a": "180 days from the deduction date for standard AP deductions, per SPS Commerce and Confido. An MCB compliance fee reportedly allows only 60 days from the MCB issue date and files through the Kroger Supplier Hub instead, per ClearChain. Once a claim is submitted it cannot be modified, so documentation has to be complete before filing."
|
|
955
|
+
},
|
|
956
|
+
{
|
|
957
|
+
"q": "What is the difference between Lavante and Supplier Connect?",
|
|
958
|
+
"a": "Lavante was Kroger's previous PRGX-hosted dispute portal. Supplier Connect is the replacement Kroger rolled out in late 2025 with the same operator, migrated historical data, and Partner Pass single sign-on, per iNymbus. The 180-day window and PRGX review did not change. Guidance published before mid-2026 still names Lavante, so treat it as stale on portal mechanics."
|
|
959
|
+
},
|
|
960
|
+
{
|
|
961
|
+
"q": "What is a Kroger ORAD fine?",
|
|
962
|
+
"a": "ORAD stands for Original Requested Arrival Date, the delivery date on your Kroger PO. Miss it and Kroger applies a late-shipment fine. Per iNymbus, ORAD is tracked against a 98% on-time threshold with a 95% case fill rate on every shipment. ORAD fines post as AR deductions on a different claim path than the numeric AP codes, per SPS Commerce."
|
|
963
|
+
},
|
|
964
|
+
{
|
|
965
|
+
"q": "How does Kroger's deduction program compare to Walmart's?",
|
|
966
|
+
"a": "Walmart runs roughly 90 AP codes, disputes through APDP, and allows up to two years on general deductions. Kroger runs eight numeric codes plus letter codes, disputes through Supplier Connect, and allows 180 days. Kroger also splits compliance fees onto a separate AR track, whereas Walmart deducts everything through the same AP flow."
|
|
967
|
+
}
|
|
968
|
+
]
|
|
969
|
+
},
|
|
970
|
+
{
|
|
971
|
+
"slug": "monday-morning-deduction-triage",
|
|
972
|
+
"title": "The 30-Minute Deduction Triage Before Your OTIF Meeting",
|
|
973
|
+
"description": "Nine checks before the weekly OTIF meeting, four timestamps that replace carrier blame, and a script that turns scorecard panic into one next action per PO.",
|
|
974
|
+
"pubDate": "2026-09-13T00:00:00.000Z",
|
|
975
|
+
"author": "Pixels and Clicks",
|
|
976
|
+
"tags": [
|
|
977
|
+
"OTIF",
|
|
978
|
+
"Deductions",
|
|
979
|
+
"Retail Compliance",
|
|
980
|
+
"Scorecard",
|
|
981
|
+
"ASN",
|
|
982
|
+
"EDI",
|
|
983
|
+
"Carrier"
|
|
984
|
+
],
|
|
985
|
+
"readingTime": 9,
|
|
986
|
+
"cluster": "prevention",
|
|
987
|
+
"draft": false,
|
|
988
|
+
"hideToc": true,
|
|
989
|
+
"image": "/images/articles/monday-morning-deduction-triage-banner.jpg",
|
|
990
|
+
"imageAlt": "OTIF deduction triage checklist with nine checks before the Monday scorecard meeting",
|
|
991
|
+
"answer": "Before blaming the carrier for an OTIF deduction, check nine things in order: PO version match, pick completion, ASN-to-pick match, ASN send time against the retailer cutoff, 997 acknowledgment, 824 content response, appointment request timing, carrier arrival time, and retailer receiving record. The first mismatch you find is your root cause. Pull four timestamps for each flagged PO before the meeting starts: pick confirm, ASN send, appointment confirmation, and retailer receipt.",
|
|
992
|
+
"answerQualifier": "Based on public EDI and compliance documentation from SPS Commerce, BOLD VAN, Confido, Endless Commerce, and DOSS, September 2026. Individual retailer scoring rules, dispute windows, and chargeback thresholds vary by program.",
|
|
993
|
+
"faq": [
|
|
994
|
+
{
|
|
995
|
+
"q": "What should I check before blaming the carrier for an OTIF deduction?",
|
|
996
|
+
"a": "Check nine things: whether the PO changed after confirmation, whether the warehouse picked the full quantity, whether the ASN matched the pick, whether the ASN transmitted before the retailer's cutoff, whether the 997 came back clean, whether an 824 flagged a content error, whether the delivery appointment was requested on time, whether the carrier arrived inside the window, and whether the retailer's receiving record matched the ASN. The first mismatch tells you where to work."
|
|
997
|
+
},
|
|
998
|
+
{
|
|
999
|
+
"q": "How do I run a 30-minute OTIF deduction meeting?",
|
|
1000
|
+
"a": "Use this order: Finance shows the deduction line and dollar amount. Ops pulls the affected POs. Warehouse shows pick completion and short-pick exceptions. The EDI owner shows ASN send time, 997, and 824 status. Logistics shows the appointment and delivery trail. Then tag each PO as dispute, fix, carrier, or unknown, and assign one next action per PO."
|
|
1001
|
+
},
|
|
1002
|
+
{
|
|
1003
|
+
"q": "What four timestamps should I pull before an OTIF meeting?",
|
|
1004
|
+
"a": "Pick confirm time (when the warehouse finished the order), ASN send time (when the retailer was told what was coming), appointment confirmation time (whether the delivery slot was real), and arrival or receipt time (whether freight hit the window). If those four don't line up, you don't have a freight issue yet. You have a timeline issue."
|
|
1005
|
+
},
|
|
1006
|
+
{
|
|
1007
|
+
"q": "Can a clean 997 mean my ASN still failed?",
|
|
1008
|
+
"a": "Yes. A 997 confirms the file parsed without syntax errors. It doesn't confirm the retailer accepted the business content: quantities, item identifiers, pack hierarchy, or shipment date. Business-level rejection comes back on the 824, if the retailer sends one. A clean 997 with no 824 follow-up is not proof of acceptance."
|
|
1009
|
+
}
|
|
1010
|
+
]
|
|
1011
|
+
},
|
|
1012
|
+
{
|
|
1013
|
+
"slug": "netsuite-edi-856-failures",
|
|
1014
|
+
"title": "The Five NetSuite Settings Behind Your ASN Rejections",
|
|
1015
|
+
"description": "Five NetSuite-specific reasons the EDI 856 ASN comes out wrong: item cross-references, UOM conversion, pick timing, subsidiary mapping, kit explosion.",
|
|
1016
|
+
"pubDate": "2026-08-13T00:00:00.000Z",
|
|
1017
|
+
"author": "Pixels and Clicks",
|
|
1018
|
+
"tags": [
|
|
1019
|
+
"EDI",
|
|
1020
|
+
"856",
|
|
1021
|
+
"NetSuite",
|
|
1022
|
+
"ERP",
|
|
1023
|
+
"ASN",
|
|
1024
|
+
"Retail Compliance"
|
|
1025
|
+
],
|
|
1026
|
+
"readingTime": 8,
|
|
1027
|
+
"cluster": "erp-technical",
|
|
1028
|
+
"draft": false,
|
|
1029
|
+
"hideToc": true,
|
|
1030
|
+
"image": "/images/articles/netsuite-edi-856-failures-banner.jpg",
|
|
1031
|
+
"imageAlt": "NetSuite's EDI 856 document failure",
|
|
1032
|
+
"answer": "A NetSuite-generated EDI 856 that's wrong at transmission becomes a shortage or no-merchandise deduction thirty to sixty days later. Five NetSuite-specific gaps cause it: item cross-references, eaches-to-cases unit conversion, pick-confirm timing, OneWorld subsidiary routing, and kit or assembly explosion into pack-level detail. Each is catchable pre-transmission with a saved search or SuiteFlow validation.",
|
|
1033
|
+
"answerQualifier": "Based on Oracle NetSuite's own help documentation (item records, units of measure, item fulfillment, OneWorld) and EDI-connector vendor documentation (Orderful, Celigo), August 2026. NetSuite's native fields and statuses are documented. Which specific validations a given connector runs pre-transmission varies by vendor and is not a public standard.",
|
|
1034
|
+
"faq": [
|
|
1035
|
+
{
|
|
1036
|
+
"q": "Does NetSuite generate the EDI 856 natively, or does it need a connector?",
|
|
1037
|
+
"a": "NetSuite's Item Fulfillment record holds most of the data an 856 needs, but NetSuite does not natively speak X12. An EDI connector (Orderful, Celigo, SPS Commerce, TrueCommerce, and others) reads the fulfillment record and maps it into the transaction set. Several connectors add custom fields to capture pallet/carton detail that Item Fulfillment does not represent on its own."
|
|
1038
|
+
},
|
|
1039
|
+
{
|
|
1040
|
+
"q": "Can a unit-of-measure mismatch cause a shortage deduction even when the physical count was correct?",
|
|
1041
|
+
"a": "Yes. If the 856 declares a quantity in eaches where the retailer's implementation guide expects cases, the receiving count looks short or over by exactly the case-pack multiplier. Nothing is physically wrong. It reads as a shortage code on the remittance regardless."
|
|
1042
|
+
},
|
|
1043
|
+
{
|
|
1044
|
+
"q": "Why does a kit or assembly item break an 856 that a simple inventory item doesn't?",
|
|
1045
|
+
"a": "A retailer's system expects pack-level detail: which item, in what quantity, in which carton. A kit item is one line in NetSuite but multiple physical components on the truck. As a result, the 856 has to explode the kit into its components at the pack level. That explosion logic lives in the connector, not in NetSuite's native fulfillment screen."
|
|
1046
|
+
},
|
|
1047
|
+
{
|
|
1048
|
+
"q": "Does a NetSuite OneWorld subsidiary structure affect EDI routing?",
|
|
1049
|
+
"a": "It can. Each OneWorld transaction generally posts to one subsidiary, and each subsidiary has its own locations. If a trading-partner or ship-to mapping points to the wrong subsidiary's location, the fulfillment record can carry the wrong facility or tax jurisdiction into the outbound 856. That's an error a receiving DC has no way to catch on its end."
|
|
1050
|
+
},
|
|
1051
|
+
{
|
|
1052
|
+
"q": "What's the fastest way to start catching these before they become deductions?",
|
|
1053
|
+
"a": "Pick the one failure mode you have already seen on a remittance and build a saved search for it first: unmapped vendor item codes, fulfillments missing a UOM conversion, or kit lines with no component detail. A single working validation beats a five-point plan that never ships."
|
|
1054
|
+
}
|
|
1055
|
+
]
|
|
1056
|
+
},
|
|
1057
|
+
{
|
|
1058
|
+
"slug": "peak-season-routing-guide-changes",
|
|
1059
|
+
"title": "What Changes in the Routing Guide From October to December",
|
|
1060
|
+
"description": "What tightens in retailer routing guides from October through December: MABD tolerance, appointment cutoffs, and ASN timing shifts, retailer by retailer.",
|
|
1061
|
+
"pubDate": "2026-09-09T00:00:00.000Z",
|
|
1062
|
+
"author": "Pixels and Clicks",
|
|
1063
|
+
"tags": [
|
|
1064
|
+
"Routing Guide",
|
|
1065
|
+
"Peak Season",
|
|
1066
|
+
"Walmart",
|
|
1067
|
+
"Target",
|
|
1068
|
+
"Home Depot",
|
|
1069
|
+
"Kroger",
|
|
1070
|
+
"OTIF",
|
|
1071
|
+
"Retail Compliance"
|
|
1072
|
+
],
|
|
1073
|
+
"readingTime": 10,
|
|
1074
|
+
"cluster": "prevention",
|
|
1075
|
+
"draft": false,
|
|
1076
|
+
"hideToc": true,
|
|
1077
|
+
"image": "/images/articles/peak-season-routing-guide-changes-banner.jpg",
|
|
1078
|
+
"imageAlt": "Whiteboard-style matrix comparing peak-season routing guide changes across Walmart, Target, Home Depot, and Kroger, with columns for MABD tolerance, appointment cutoff, ASN cutoff, and receiving behavior",
|
|
1079
|
+
"answer": "The core routing rules do not always change for peak season, but the tolerance around them almost always does. Walmart holds the Must Arrive By Date window through peak but runs it against higher volume, so misses compound. Target compresses appointment windows in the last two weeks of November and December at high-volume DCs. Home Depot publishes peak-period addenda through its Vendor Compliance program. Kroger tightens receiving appointment cadence at high-volume DCs during peak. The pattern across all four is that measurement rules stay the same, and enforcement gets stricter.",
|
|
1080
|
+
"answerQualifier": "Based on public routing guide and vendor compliance documentation from Walmart, Target, Home Depot, Kroger, and industry vendor sources including SPS Commerce, SupplyPike, Confido, and Supply Chain Dive, September 2026. Retailer routing guides are updated by supplier portal notice and are not always publicly documented in full. Confirm current specifics in the relevant retailer portal before acting.",
|
|
1081
|
+
"faq": [
|
|
1082
|
+
{
|
|
1083
|
+
"q": "What is a retailer routing guide, and why does it change for peak season?",
|
|
1084
|
+
"a": "A retailer routing guide is the retailer's rulebook for how freight arrives at its DCs: MABD dates, appointment procedures, carrier selection, load consolidation, and ASN cutoffs. The rules themselves rarely change for peak. What changes is the tolerance: fewer late-appointment overrides, tighter enforcement of load-consolidation rules, faster dock rejections when paperwork is off. Peak is when the routing guide gets enforced to the letter, not when the letter gets rewritten."
|
|
1085
|
+
},
|
|
1086
|
+
{
|
|
1087
|
+
"q": "Does Walmart change MABD tolerance in November and December?",
|
|
1088
|
+
"a": "Walmart's MABD window and OTIF measurement thresholds have been publicly reported through the Retail Link portal rather than external press. Public reporting suggests Walmart holds the 90 percent on-time and 95 percent in-full targets for prepaid suppliers across the year, but the aggregate volume denominator during peak means small absolute misses cost more OTIF points than the same misses in June. Suppliers who track the fine dollar exposure rather than the percentage often see a threefold peak-to-mid-year variance without any rule change."
|
|
1089
|
+
},
|
|
1090
|
+
{
|
|
1091
|
+
"q": "How much lead time does Target require for peak appointments?",
|
|
1092
|
+
"a": "Target's OTIF program uses MABD-based on-time measurement and appointment procedures documented in its vendor portal. Public vendor coverage indicates Target compresses appointment windows at high-volume DCs during peak, particularly in the two weeks leading up to Thanksgiving and Christmas. Specific cutoff hours are not publicly documented in full and vary by DC. Confirm the current Target Vendor Standards Manual and any peak addenda through Target Partners Online before shipping."
|
|
1093
|
+
},
|
|
1094
|
+
{
|
|
1095
|
+
"q": "What does Home Depot publish about peak-period routing?",
|
|
1096
|
+
"a": "Home Depot maintains a Vendor Compliance program with a Supplier Expectation Rating (SER) and disputes route through Vendor Compliance Support. Home Depot publishes peak-period addenda to its supplier community through Vendor Standards updates. Public vendor coverage suggests these addenda cover appointment window compression at high-volume DCs from October through December, plus stricter enforcement of load-tender response times. Full addendum contents are not publicly documented; check Home Depot's supplier portal for current specifics."
|
|
1097
|
+
},
|
|
1098
|
+
{
|
|
1099
|
+
"q": "Does Kroger tighten routing rules for peak?",
|
|
1100
|
+
"a": "Kroger operates supplier compliance through its supplier hub and Sync platform, with deduction and chargeback programs tied to shipment execution against the PO and MABD. Kroger runs a large peak grocery period around Thanksgiving and Christmas, and public vendor coverage indicates receiving appointment cadence tightens at high-volume DCs during that window. Kroger does not publish peak-specific addenda as broadly as some other retailers; the current shipment and routing rules are documented in the Kroger Supplier Hub."
|
|
1101
|
+
}
|
|
1102
|
+
]
|
|
1103
|
+
},
|
|
1104
|
+
{
|
|
1105
|
+
"slug": "q4-deduction-cliff-calendar",
|
|
1106
|
+
"title": "The Q4 Deduction Cliff: A Month-by-Month Calendar",
|
|
1107
|
+
"description": "Retailer deductions do not spike evenly across Q4. OTIF fines hit in November, shortages pile up in December, the returns wave crests in January. The calendar.",
|
|
1108
|
+
"pubDate": "2026-09-05T00:00:00.000Z",
|
|
1109
|
+
"author": "Pixels and Clicks",
|
|
1110
|
+
"tags": [
|
|
1111
|
+
"Deductions",
|
|
1112
|
+
"Q4",
|
|
1113
|
+
"Peak Season",
|
|
1114
|
+
"OTIF",
|
|
1115
|
+
"Retail Compliance",
|
|
1116
|
+
"Chargebacks"
|
|
1117
|
+
],
|
|
1118
|
+
"readingTime": 10,
|
|
1119
|
+
"cluster": "prevention",
|
|
1120
|
+
"draft": false,
|
|
1121
|
+
"hideToc": true,
|
|
1122
|
+
"image": "/images/articles/q4-deduction-cliff-calendar-banner.jpg",
|
|
1123
|
+
"imageAlt": "Whiteboard-style calendar diagram of the Q4 deduction cliff for CPG suppliers, showing OTIF fines peaking in November, shortage claims peaking in December, and returns and markdown deductions peaking in January and February",
|
|
1124
|
+
"answer": "The Q4 deduction cliff runs October through February and hits three separate waves. OTIF fines and ASN failures peak in November when volume is highest against the tightest routing windows. Shortage and receiving claims peak in December when DC receiving speeds up and error rates rise. Markdown deductions under code 10 and returns under codes 92, 93, and 94 peak in January and February, after post-holiday sell-through gets counted. A supplier that plans against one flat Q4 chargeback rate underestimates the risk in each specific window.",
|
|
1125
|
+
"answerQualifier": "Based on public deduction and OTIF documentation from BOLD VAN, Endless Commerce, SPS Commerce, SupplyPike, and Supply Chain Dive, September 2026. Retailer deduction volumes and program details vary by account and year.",
|
|
1126
|
+
"faq": [
|
|
1127
|
+
{
|
|
1128
|
+
"q": "Which deduction types actually spike in Q4?",
|
|
1129
|
+
"a": "Three families spike, at different times. OTIF fines and ASN-related chargebacks peak in November because peak volume runs against tighter routing windows. Shortage and receiving deductions like Walmart code 22 and Target SIFR peak in December because DC receiving throughput rises and error rates rise with it. Markdown deductions like Walmart code 10 and returns under codes 92, 93, and 94 peak in January and February, when the retailer counts through post-holiday sell-through and returns."
|
|
1130
|
+
},
|
|
1131
|
+
{
|
|
1132
|
+
"q": "When does the peak-season OTIF fine window end?",
|
|
1133
|
+
"a": "The measurement window and the payment window are different. The measurement window at Walmart, Target, and Kroger typically covers the receiving month, so a November miss shows up on your November scorecard. The fine itself often lands on the following month's remittance, so a November scorecard fine may not hit your check until late December or January. If your team measures deduction risk by remittance date rather than shipment date, the November miss looks like a January problem, and the root cause looks blurry."
|
|
1134
|
+
},
|
|
1135
|
+
{
|
|
1136
|
+
"q": "Why do returns deductions land in January instead of during the holiday?",
|
|
1137
|
+
"a": "Retailers batch returns processing. Consumer returns from Black Friday and December sales sit in stores or reverse-logistics centers for weeks before they process against your account. Walmart returns codes 92, 93, and 94 typically show up on remittances 30 to 90 days after the Christmas peak. That is why the January remittance often runs materially larger than any month in Q4 itself. The volume is there, it is just not counted yet."
|
|
1138
|
+
},
|
|
1139
|
+
{
|
|
1140
|
+
"q": "Should I reserve dispute capacity for Q4, or spread it evenly?",
|
|
1141
|
+
"a": "Do not spread it evenly. Endless Commerce reports dispute win rates of 75 to 80 percent when filed within seven days and 15 to 20 percent after 60 days. Your November OTIF fine hits your check in December. Your December shortage claim hits in January. Your January returns hit in February. If your dispute team is running at capacity through the peak, they miss the seven-day window on the exact deductions with the highest recovery odds. Staff the dispute window to the calendar, not to an average month."
|
|
1142
|
+
},
|
|
1143
|
+
{
|
|
1144
|
+
"q": "How large is a typical Q4 deduction cliff for a $50M CPG supplier?",
|
|
1145
|
+
"a": "Deduction burden varies with retailer mix and program details, but a common pattern for a $50 million CPG supplier at a Walmart, Target, Amazon 1P, and Kroger mix: November through February deductions run 1.5 to 3 times the mid-year monthly average, driven by OTIF, shortage, and returns codes in sequence. That is $50,000 to $150,000 of additional exposure across the four-month window compared to a mid-year baseline, before any specific program change lands."
|
|
1146
|
+
}
|
|
1147
|
+
]
|
|
1148
|
+
},
|
|
1149
|
+
{
|
|
1150
|
+
"slug": "read-walmart-remittance-advice",
|
|
1151
|
+
"title": "How to Read a Walmart Remittance and Spot the Disputes",
|
|
1152
|
+
"description": "Where the invoice number, PO number, and deduction code live on a Walmart remittance, and how to spot which lines are worth disputing.",
|
|
1153
|
+
"pubDate": "2026-08-09T00:00:00.000Z",
|
|
1154
|
+
"author": "Pixels and Clicks",
|
|
1155
|
+
"tags": [
|
|
1156
|
+
"Walmart",
|
|
1157
|
+
"Remittance Advice",
|
|
1158
|
+
"Deduction Codes",
|
|
1159
|
+
"APDP",
|
|
1160
|
+
"Retail Compliance"
|
|
1161
|
+
],
|
|
1162
|
+
"readingTime": 8,
|
|
1163
|
+
"cluster": "prevention",
|
|
1164
|
+
"draft": false,
|
|
1165
|
+
"hideToc": true,
|
|
1166
|
+
"image": "/images/articles/read-walmart-remittance-advice-banner.jpg",
|
|
1167
|
+
"imageAlt": "Hand-drawn whiteboard-style diagram explaining how to read a Walmart remittance advice: the payment total, invoice reference block, and deduction code line labeled with arrows, plus a checklist equation for matching a code to a claim type",
|
|
1168
|
+
"answer": "A Walmart remittance advice is the payment document, an EDI 820, showing what was paid against each invoice and what was subtracted first. Deduction lines carry a numeric code, a dollar amount, and a reference back to the invoice or PO. Reading one means matching that code to a claim type, then deciding if the line is worth disputing.",
|
|
1169
|
+
"answerQualifier": "Based on the public X12 820 transaction-set structure (SPS Commerce's EDI reference), vendor guides to Walmart's Accounts Payable Dispute Portal and APIS search fields (SPS Commerce, iNymbus), and a 2025 industry benchmark on deduction write-off rates (Finortal, cited via OverDeduct), August 2026.",
|
|
1170
|
+
"faq": [
|
|
1171
|
+
{
|
|
1172
|
+
"q": "Why is my Walmart check short?",
|
|
1173
|
+
"a": "It's not a check for the invoice total. It's a check for the invoice total minus every deduction line Walmart's system applied first. Each deduction carries a code and a reason, and the check reflects the net after all of them."
|
|
1174
|
+
},
|
|
1175
|
+
{
|
|
1176
|
+
"q": "Where do I find what a Walmart deduction code means?",
|
|
1177
|
+
"a": "The code itself appears on the remittance line, next to the amount and a reference back to the invoice or PO. What the code means isn't printed there. Look it up separately, in Walmart's own Retail Link documentation or a fact-checked reference like this site's deduction-code hub."
|
|
1178
|
+
},
|
|
1179
|
+
{
|
|
1180
|
+
"q": "Should I dispute every deduction on a Walmart remittance?",
|
|
1181
|
+
"a": "No. Vendor sources point to frequency as the better signal, not size. One or two deductions in a cycle usually means a one-off error, worth a quick dispute. The same code every cycle points to a process problem upstream, worth fixing at the root."
|
|
1182
|
+
},
|
|
1183
|
+
{
|
|
1184
|
+
"q": "How long do I have to respond once I open a Walmart dispute?",
|
|
1185
|
+
"a": "Per vendor documentation of the Accounts Payable Dispute Portal, a draft dispute expires automatically after 14 days if not submitted. A case Walmart marks 'Supplier Action' auto-closes if you don't respond within 7 days. The overall claim-dispute deadline for a given code is separate and varies. It isn't confirmed here."
|
|
1186
|
+
}
|
|
1187
|
+
]
|
|
1188
|
+
},
|
|
1189
|
+
{
|
|
1190
|
+
"slug": "reduce-amazon-vendor-central-chargeback-fees",
|
|
1191
|
+
"title": "The Five Amazon 1P Chargebacks That Cost Vendors Most",
|
|
1192
|
+
"description": "The five Amazon 1P chargeback categories that generate the most fees, what triggers each, the prevention step for each, and which you can still dispute.",
|
|
1193
|
+
"pubDate": "2026-09-11T00:00:00.000Z",
|
|
1194
|
+
"author": "Pixels and Clicks",
|
|
1195
|
+
"tags": [
|
|
1196
|
+
"Amazon 1P",
|
|
1197
|
+
"Vendor Central",
|
|
1198
|
+
"Chargebacks",
|
|
1199
|
+
"OTIF",
|
|
1200
|
+
"ASN",
|
|
1201
|
+
"Compliance",
|
|
1202
|
+
"Deductions"
|
|
1203
|
+
],
|
|
1204
|
+
"readingTime": 9,
|
|
1205
|
+
"cluster": "prevention",
|
|
1206
|
+
"draft": false,
|
|
1207
|
+
"hideToc": true,
|
|
1208
|
+
"image": "/images/articles/reduce-amazon-vendor-central-chargeback-fees-banner.jpg",
|
|
1209
|
+
"imageAlt": "Amazon 1P chargeback categories: PO on-time, ASN accuracy, carton labels, barcodes, and prep, each with a prevention step",
|
|
1210
|
+
"answer": "You reduce Amazon Vendor Central chargeback fees by fixing the root cause of each recurring defect, not by disputing charges one at a time. Five categories generate most of the money: PO On-Time Accuracy, ASN Accuracy, Carton Content Accuracy, Non-Compliant Barcode, and prep or packaging failures. Each is preventable before the shipment leaves your dock.",
|
|
1211
|
+
"answerQualifier": "Compiled from public vendor-compliance sources (SPS Commerce / SupplierWiki, Consulterce, iNymbus, RT7 Digital, SalesDuo, Endless Commerce, Amazowl), September 2026. Fee percentages and per-unit amounts are vendor-reported, vary by region and program update, and are flagged inline. Confirm the figure that applies to you in Vendor Central under Operational Performance.",
|
|
1212
|
+
"faq": [
|
|
1213
|
+
{
|
|
1214
|
+
"q": "How much do Amazon vendor chargebacks cost?",
|
|
1215
|
+
"a": "Vendor recovery firms report total chargeback exposure running as high as 5% of Amazon revenue, roughly $5,000 per $100,000, for vendors with unaddressed defects (SalesDuo). Individual fees vary by type: PO On-Time Accuracy is reported at 3% of product cost, rising to 10% for units never shipped (Amazowl, Consulterce). ASN Accuracy is reported at 2 to 6% of cost of goods (Consulterce). A case-pack barcode defect is reported at $26 per non-compliant unit (SPS Commerce). Your own Operational Performance report in Vendor Central has the figures that apply to your account."
|
|
1216
|
+
},
|
|
1217
|
+
{
|
|
1218
|
+
"q": "Can you dispute an Amazon vendor chargeback?",
|
|
1219
|
+
"a": "Yes. Amazon gives you 30 days from the chargeback notification to dispute it in Vendor Central, and two dispute attempts per chargeback. Multiple vendor sources confirm both. RT7 Digital reports a roughly 70% success rate when the dispute includes a complete evidence set: EDI transmission logs, carrier proof of delivery, and appointment confirmations."
|
|
1220
|
+
},
|
|
1221
|
+
{
|
|
1222
|
+
"q": "What is the most common Amazon vendor chargeback?",
|
|
1223
|
+
"a": "PO On-Time Accuracy and ASN Accuracy are the two categories vendors cite most often. PO On-Time Accuracy fires when confirmed units miss the delivery window. ASN Accuracy fires when the Advance Ship Notice does not match what the fulfillment center receives at the unit level. Both hit shipments that otherwise look clean."
|
|
1224
|
+
},
|
|
1225
|
+
{
|
|
1226
|
+
"q": "What is OTIF for Amazon vendors?",
|
|
1227
|
+
"a": "OTIF means on-time, in-full. For Amazon 1P it maps to PO On-Time Accuracy: the units Amazon confirmed on the purchase order have to arrive inside the required window and match the confirmed quantity. A short shipment and a late shipment are measured separately, and a single delivery can fail both. See [what OTIF actually costs](/articles/what-is-otif.html)."
|
|
1228
|
+
},
|
|
1229
|
+
{
|
|
1230
|
+
"q": "Does disputing a chargeback stop it from happening again?",
|
|
1231
|
+
"a": "No. A dispute recovers one fee. It does nothing to the process that produced it. If your ERP builds the ASN from the order quantity instead of the confirmed pick, the next shipment carries the same defect and the same chargeback. Reducing the fee means changing where the data comes from, not winning the dispute."
|
|
1232
|
+
}
|
|
1233
|
+
]
|
|
1234
|
+
},
|
|
1235
|
+
{
|
|
1236
|
+
"slug": "retail-deduction-evidence-pack",
|
|
1237
|
+
"title": "The Six Documents You Need Before Disputing a Deduction",
|
|
1238
|
+
"description": "The six documents that turn a deduction dispute into a case: what each one proves, what it doesn't, and the order to pull them before the window closes.",
|
|
1239
|
+
"pubDate": "2026-09-03T00:00:00.000Z",
|
|
1240
|
+
"author": "Pixels and Clicks",
|
|
1241
|
+
"tags": [
|
|
1242
|
+
"Deductions",
|
|
1243
|
+
"Retail Compliance",
|
|
1244
|
+
"EDI",
|
|
1245
|
+
"ASN",
|
|
1246
|
+
"OTIF",
|
|
1247
|
+
"Dispute"
|
|
1248
|
+
],
|
|
1249
|
+
"readingTime": 9,
|
|
1250
|
+
"cluster": "prevention",
|
|
1251
|
+
"draft": false,
|
|
1252
|
+
"hideToc": true,
|
|
1253
|
+
"image": "/images/articles/retail-deduction-evidence-pack-banner.jpg",
|
|
1254
|
+
"imageAlt": "Deduction evidence checklist: PO, pick ticket, ASN, BOL, POD, invoice, and retailer receipt linked in a chain",
|
|
1255
|
+
"answer": "A retail deduction evidence pack is the set of documents you assemble before filing a dispute: purchase order, pick ticket, EDI 856 ASN, bill of lading, proof of delivery, EDI 997 and 824 acknowledgments, invoice, and retailer receiving record. Each document proves one link in the chain. A POD proves the truck arrived. It doesn't prove the ASN was accepted or the invoice matched the PO. You need the full chain.",
|
|
1256
|
+
"answerQualifier": "Based on the public X12 EDI standard, SPS Commerce and Orderful supplier documentation, and Inmar and OverDeduct industry benchmarks, September 2026. Individual retailer dispute requirements vary by program.",
|
|
1257
|
+
"faq": [
|
|
1258
|
+
{
|
|
1259
|
+
"q": "What documents do I need to dispute a retail deduction?",
|
|
1260
|
+
"a": "You need the purchase order, pick ticket or warehouse shipment record, EDI 856 ASN, EDI 997 functional acknowledgment, EDI 824 application advice (if the retailer sends one), bill of lading, proof of delivery, invoice, and the retailer's own receiving record. Each proves one link. The gap between any two adjacent documents is where the deduction started."
|
|
1261
|
+
},
|
|
1262
|
+
{
|
|
1263
|
+
"q": "Does a proof of delivery prove a shortage deduction is wrong?",
|
|
1264
|
+
"a": "A POD proves delivery happened. It doesn't prove the delivered quantity matched the ASN, the invoice, or the purchase order. A shortage deduction compares multiple quantities: ordered, picked, ASN'd, and received. The POD covers only one of those. You still need the other documents to show where the count diverged."
|
|
1265
|
+
},
|
|
1266
|
+
{
|
|
1267
|
+
"q": "Does a clean EDI 997 mean the retailer accepted my ASN?",
|
|
1268
|
+
"a": "A 997 confirms the file parsed without syntax errors. It doesn't confirm the retailer accepted the business content, the quantities, the item identifiers, or the pack hierarchy. Business-level acceptance or rejection comes back on the EDI 824, if the retailer uses one. Treating the 997 as approval is one of the most common evidence gaps in deduction disputes."
|
|
1269
|
+
},
|
|
1270
|
+
{
|
|
1271
|
+
"q": "How long do I have to dispute a retail deduction?",
|
|
1272
|
+
"a": "Dispute windows vary by retailer. Walmart uses multiple windows depending on claim type: up to 2 years from invoice date for general AP deductions, 12 months for shortage claims, and 15 to 30 days for AP chargebacks. Amazon gives 30 days with two dispute attempts. Target and Kroger each set their own windows by claim type. See our deduction dispute deadlines by retailer for the current reported windows."
|
|
1273
|
+
}
|
|
1274
|
+
]
|
|
1275
|
+
},
|
|
1276
|
+
{
|
|
1277
|
+
"slug": "retail-ready-vs-distribution-ready",
|
|
1278
|
+
"title": "You Shipped to the DC. Why Are Deductions Already Stacking Up?",
|
|
1279
|
+
"description": "In distribution does not mean retail-ready. The six operational gaps that turn a first retail PO into deductions, and how to close them before shipment.",
|
|
1280
|
+
"pubDate": "2026-09-17T00:00:00.000Z",
|
|
1281
|
+
"author": "Pixels and Clicks",
|
|
1282
|
+
"tags": [
|
|
1283
|
+
"Retail Compliance",
|
|
1284
|
+
"OTIF",
|
|
1285
|
+
"EDI",
|
|
1286
|
+
"Deductions",
|
|
1287
|
+
"CPG",
|
|
1288
|
+
"Supply Chain"
|
|
1289
|
+
],
|
|
1290
|
+
"readingTime": 10,
|
|
1291
|
+
"cluster": "prevention",
|
|
1292
|
+
"draft": false,
|
|
1293
|
+
"hideToc": true,
|
|
1294
|
+
"image": "/images/articles/retail-ready-vs-distribution-ready-banner.jpg",
|
|
1295
|
+
"imageAlt": "Two side-by-side checklists comparing distribution-ready and retail-ready CPG supplier operations",
|
|
1296
|
+
"answer": "A CPG supplier is distribution-ready when it can ship product to a warehouse. It is retail-ready when every shipment meets a retailer's specific compliance rules for EDI, labeling, packaging, delivery windows, and invoicing. The gap between the two is where deductions start. Deductions run 5 to 15% of gross sales across the CPG sector, and most trace back to operational mismatches, not product defects. Closing the six gaps before the first PO ships is cheaper than disputing chargebacks after.",
|
|
1297
|
+
"answerQualifier": "Based on public vendor compliance documentation from Bravo CPG, SPS Commerce, Productiv, Inmar, and OverDeduct benchmarks, September 2026. Individual retailer compliance thresholds and penalty structures vary by program.",
|
|
1298
|
+
"faq": [
|
|
1299
|
+
{
|
|
1300
|
+
"q": "What is the difference between distribution-ready and retail-ready?",
|
|
1301
|
+
"a": "Distribution-ready means your product can reach a warehouse: you have packaging, a logistics partner, and a way to take orders. Retail-ready means every shipment meets the retailer's specific operational rules for EDI transmission, labeling format, packaging configuration, delivery timing, and invoicing accuracy. The difference is compliance, not capability."
|
|
1302
|
+
},
|
|
1303
|
+
{
|
|
1304
|
+
"q": "What percentage of revenue do CPG brands lose to retail deductions?",
|
|
1305
|
+
"a": "Inmar reports that deductions account for 5 to 15% of gross sales in the CPG sector. For mid-market brands, Finortal's 2025 benchmark puts the write-off rate at 1.2 to 2.4% of gross revenue annually. On a $15M brand, that write-off alone is $180K to $360K per year."
|
|
1306
|
+
},
|
|
1307
|
+
{
|
|
1308
|
+
"q": "What are the most common retail compliance failures for new CPG suppliers?",
|
|
1309
|
+
"a": "The most common failures are ASN accuracy mismatches between the advance ship notice and physical shipment, routing guide violations from not reading retailer-specific requirements, incomplete or incorrect labeling, missed delivery windows, and invoice discrepancies against the purchase order. Each failure generates its own chargeback category."
|
|
1310
|
+
},
|
|
1311
|
+
{
|
|
1312
|
+
"q": "How do I make my CPG brand retail-ready before the first PO?",
|
|
1313
|
+
"a": "Map six areas before the first shipment: EDI capability and testing, GS1-128 labeling compliance, retailer-specific packaging configuration, delivery window and OTIF threshold awareness, invoice-to-PO matching rules, and a dispute process for when chargebacks arrive anyway. One person owning the weekly PO review reportedly reduces chargebacks without requiring infrastructure changes."
|
|
1314
|
+
}
|
|
1315
|
+
]
|
|
1316
|
+
},
|
|
1317
|
+
{
|
|
1318
|
+
"slug": "retail-vendor-compliance",
|
|
1319
|
+
"title": "Retail Vendor Compliance: The Rulebook That Decides Your Margin",
|
|
1320
|
+
"description": "Retail vendor compliance is the routing-guide rulebook that turns a shipping, labeling, or EDI miss into a chargeback. What retailers grade, what it costs, and where to fix it.",
|
|
1321
|
+
"pubDate": "2026-11-07T00:00:00.000Z",
|
|
1322
|
+
"author": "Pixels and Clicks",
|
|
1323
|
+
"tags": [
|
|
1324
|
+
"Vendor Compliance",
|
|
1325
|
+
"Retail Compliance",
|
|
1326
|
+
"Chargebacks",
|
|
1327
|
+
"CPG",
|
|
1328
|
+
"Supply Chain"
|
|
1329
|
+
],
|
|
1330
|
+
"readingTime": 4,
|
|
1331
|
+
"cluster": "prevention",
|
|
1332
|
+
"draft": false,
|
|
1333
|
+
"hideToc": true,
|
|
1334
|
+
"pillarOrder": 1,
|
|
1335
|
+
"pillarLabel": "Vendor Compliance",
|
|
1336
|
+
"pillarBlurb": "The retailer rulebook: what gets graded, and how a single miss becomes a chargeback.",
|
|
1337
|
+
"image": "/images/articles/retail-vendor-compliance-banner.jpg",
|
|
1338
|
+
"imageAlt": "Hand-drawn whiteboard diagram showing a retailer routing guide, a shipment scanned at receiving, a flagged violation, and the resulting deduction on a remittance",
|
|
1339
|
+
"answer": "Retail vendor compliance is the set of rules a retailer publishes in its routing guide and vendor agreement covering how you ship, label, pack, and invoice. Break a rule and the retailer issues a chargeback, a deduction pulled off your payment, even when the product itself arrived complete and on time.",
|
|
1340
|
+
"answerQualifier": "Based on retailer compliance terms documented across this site's OTIF and EDI coverage, plus industry description from SPS Commerce, November 2026. Routing guides change without notice; confirm current terms in your own vendor portal.",
|
|
1341
|
+
"faq": [
|
|
1342
|
+
{
|
|
1343
|
+
"q": "What is vendor compliance in retail?",
|
|
1344
|
+
"a": "Vendor compliance is shipping to the specification a retailer publishes in its routing guide and vendor agreement: the delivery window, the pallet and carton configuration, the labels, the EDI documents, and the invoice format. Each retailer writes its own rulebook, so a supplier selling into Walmart, Target, Kroger, and Amazon manages four separate compliance programs at once."
|
|
1345
|
+
},
|
|
1346
|
+
{
|
|
1347
|
+
"q": "What is a vendor compliance chargeback?",
|
|
1348
|
+
"a": "A chargeback is a deduction the retailer takes off your payment when a shipment breaks a routing-guide rule. It posts as a coded line on your remittance weeks after delivery. Unlike a product return, it has nothing to do with whether the goods were good. It is a fine for how the shipment or its paperwork failed to match the spec."
|
|
1349
|
+
},
|
|
1350
|
+
{
|
|
1351
|
+
"q": "How much do retail compliance chargebacks cost?",
|
|
1352
|
+
"a": "Per-shipment penalties commonly run 1% to 5% of the affected invoice. Walmart applies 3% of cost of goods to non-compliant cases and Target applies 5% with a $150 minimum. Deduction-recovery vendors estimate the total drag at 2% to 5% of gross revenue across a supplier's book, and that 40% to 60% of the charges are preventable or invalid."
|
|
1353
|
+
},
|
|
1354
|
+
{
|
|
1355
|
+
"q": "What are the most common vendor compliance violations?",
|
|
1356
|
+
"a": "The five domains retailers grade are EDI and ASN accuracy, on-time delivery, in-full quantity, labeling and carton configuration, and routing and packaging. Many of these trace back to a data or document mismatch in the ERP or EDI setup rather than anything that happened on the warehouse floor."
|
|
1357
|
+
},
|
|
1358
|
+
{
|
|
1359
|
+
"q": "How do you dispute a vendor compliance chargeback?",
|
|
1360
|
+
"a": "Each retailer runs its own dispute portal and deadline clock, from Walmart's APDP in Retail Link to Amazon's Vendor Central. You need the shipment evidence, meaning the ASN, the bill of lading, and proof of delivery, filed before the window closes. The dispute deadline is the difference between a recoverable charge and a permanent one."
|
|
1361
|
+
}
|
|
1362
|
+
]
|
|
1363
|
+
},
|
|
1364
|
+
{
|
|
1365
|
+
"slug": "retailer-vs-distributor-deductions-where-pnc-fits",
|
|
1366
|
+
"title": "Retailer vs. Distributor Deductions: Which Ones Your Supply Chain Team Can Actually Fix",
|
|
1367
|
+
"description": "Both say 'shortage' on the remittance. One traces to your ASN, the other to a promotional agreement your broker negotiated. A sorting guide for CPG suppliers selling through both channels.",
|
|
1368
|
+
"pubDate": "2026-10-13T00:00:00.000Z",
|
|
1369
|
+
"author": "Pixels and Clicks",
|
|
1370
|
+
"tags": [
|
|
1371
|
+
"Deductions",
|
|
1372
|
+
"CPG",
|
|
1373
|
+
"Distributors",
|
|
1374
|
+
"KeHE",
|
|
1375
|
+
"UNFI",
|
|
1376
|
+
"Walmart",
|
|
1377
|
+
"Amazon",
|
|
1378
|
+
"Scoping",
|
|
1379
|
+
"OTIF",
|
|
1380
|
+
"ASN",
|
|
1381
|
+
"EDI",
|
|
1382
|
+
"Trade Promotion"
|
|
1383
|
+
],
|
|
1384
|
+
"readingTime": 7,
|
|
1385
|
+
"cluster": "scoping",
|
|
1386
|
+
"hub": "deduction-management-for-cpg-suppliers",
|
|
1387
|
+
"draft": false,
|
|
1388
|
+
"hideToc": true,
|
|
1389
|
+
"image": "/images/articles/retailer-vs-distributor-deductions-where-pnc-fits-banner.jpg",
|
|
1390
|
+
"imageAlt": "Two remittance printouts side by side labeled retailer and distributor with a small overlap circle below",
|
|
1391
|
+
"answer": "Retailer deductions trace to compliance scorecards, ASN discrepancies, and EDI failures you can diagnose from your own warehouse and shipping data. Distributor deductions trace to promotional agreements, manufacturer chargebacks, and trade-fund contracts that need a trade-promotion audit. The overlap is small: distributor fill-rate or labeling compliance fees that borrow retailer mechanics.",
|
|
1392
|
+
"answerQualifier": "Based on published supplier compliance documentation from SPS Commerce, SupplyPike/SupplierWiki, KeHE supplier policies, UNFI supplier compliance guides, and retailer program documentation from Walmart, Amazon, Target, and Kroger. October 2026.",
|
|
1393
|
+
"faq": [
|
|
1394
|
+
{
|
|
1395
|
+
"q": "What is the difference between a retailer deduction and a distributor deduction?",
|
|
1396
|
+
"a": "A retailer deduction comes from a retailer like Walmart or Amazon and references a compliance scorecard, a receiving count, or an EDI document. A distributor deduction comes from a distributor like KeHE or UNFI and references a promotional agreement, a manufacturer chargeback, a trade-fund contract, or a broker settlement. The backing documents, the dispute paths, and the specialists who resolve them are different."
|
|
1397
|
+
},
|
|
1398
|
+
{
|
|
1399
|
+
"q": "Can a distributor charge an OTIF-style fine?",
|
|
1400
|
+
"a": "Yes. KeHE's GBB 2.0 scorecard weights fill rate at roughly 12.5 percent of the overall supplier grade, and UNFI charges a reported $250 fee for shipments arriving more than 30 minutes late. These are operational compliance fees that borrow the retailer's OTIF mechanics. They are the small overlap between the two categories."
|
|
1401
|
+
},
|
|
1402
|
+
{
|
|
1403
|
+
"q": "Does Pixels and Clicks diagnose distributor deductions?",
|
|
1404
|
+
"a": "Pixels and Clicks diagnoses operational deductions that trace to your warehouse, your ASN, or your EDI configuration. Most distributor deductions trace to contracts, promotional agreements, and broker settlements instead. Pixels and Clicks can help with the narrow overlap: a distributor's fill-rate or labeling compliance fee that behaves like a retailer OTIF fine. For the rest, a trade-promotion management firm or a broker reconciliation team is the right specialist."
|
|
1405
|
+
},
|
|
1406
|
+
{
|
|
1407
|
+
"q": "What types of deductions does KeHE take from suppliers?",
|
|
1408
|
+
"a": "KeHE groups its deductions into three categories: KeHE fees (MCB chargebacks, extra-performance fees, CONNECT BI allowances), unsaleables (underperforming, non-conforming, or spoiled product with a per-unit processing fee), and invoice adjustments. KeHE also charges an 8 percent fee on manufacturer chargebacks with a $65 per-DC minimum, per SPS Commerce."
|
|
1409
|
+
},
|
|
1410
|
+
{
|
|
1411
|
+
"q": "Should I use the same firm for retailer and distributor deduction recovery?",
|
|
1412
|
+
"a": "Usually not. Retailer deductions need access to your warehouse management system, your EDI transaction history, and the retailer's compliance scorecard. Distributor deductions need access to the trade-promotion agreement, the broker's settlement reports, and the distributor's invoice detail. Different data, different resolution paths, different expertise."
|
|
1413
|
+
}
|
|
1414
|
+
]
|
|
1415
|
+
},
|
|
1416
|
+
{
|
|
1417
|
+
"slug": "supplier-scorecard-for-cpg-suppliers",
|
|
1418
|
+
"title": "Supplier Scorecard: How Retailers Grade You, and What a Bad Score Costs",
|
|
1419
|
+
"description": "A supplier scorecard is how a retailer grades your OTIF, fill rate, and ASN accuracy. What Walmart, Target, and Amazon measure, the thresholds that trigger review, and how a bad score becomes deductions.",
|
|
1420
|
+
"pubDate": "2026-11-07T00:00:00.000Z",
|
|
1421
|
+
"author": "Pixels and Clicks",
|
|
1422
|
+
"tags": [
|
|
1423
|
+
"Supplier Scorecard",
|
|
1424
|
+
"Vendor Scorecard",
|
|
1425
|
+
"OTIF",
|
|
1426
|
+
"CPG",
|
|
1427
|
+
"Retail Compliance"
|
|
1428
|
+
],
|
|
1429
|
+
"readingTime": 4,
|
|
1430
|
+
"cluster": "scoping",
|
|
1431
|
+
"draft": false,
|
|
1432
|
+
"hideToc": true,
|
|
1433
|
+
"pillarOrder": 3,
|
|
1434
|
+
"pillarLabel": "Supplier Scorecard",
|
|
1435
|
+
"pillarBlurb": "How retailers grade you, and how a bad score turns into deductions and delisting.",
|
|
1436
|
+
"image": "/images/articles/supplier-scorecard-banner.jpg",
|
|
1437
|
+
"imageAlt": "Hand-drawn whiteboard diagram of a retailer supplier scorecard grading on-time delivery, fill rate, and ASN accuracy, with a low score flagging into review and deductions",
|
|
1438
|
+
"answer": "A supplier scorecard is the report card a retailer keeps on each vendor, grading on-time delivery, in-full fill rate, ASN and EDI accuracy, and compliance. Walmart, Target, and Amazon each run their own version. A low score triggers review, fines, and eventually delisting, so the scorecard is the leading indicator of a supplier's deduction risk.",
|
|
1439
|
+
"answerQualifier": "Based on retailer scorecard metrics documented across this site's OTIF, fill-rate, and ASN coverage, November 2026. Each retailer sets its own thresholds and changes them; confirm current terms in your own vendor portal.",
|
|
1440
|
+
"faq": [
|
|
1441
|
+
{
|
|
1442
|
+
"q": "What is a supplier scorecard?",
|
|
1443
|
+
"a": "A supplier scorecard, also called a vendor scorecard, is how a retailer measures a vendor's performance over time. It grades delivery, fill rate, documentation accuracy, and compliance, usually against a target the retailer sets. The score drives whether you keep favorable terms, land on a corrective-action plan, or face review and deductions, so it is the retailer's single clearest signal of how you are doing as a supplier."
|
|
1444
|
+
},
|
|
1445
|
+
{
|
|
1446
|
+
"q": "What metrics are on a supplier scorecard?",
|
|
1447
|
+
"a": "The core metrics are on-time delivery, in-full fill rate, and ASN or EDI accuracy, often rolled up as OTIF. Retailers add compliance measures for labeling, routing, and packaging, and some include quality and invoice accuracy. On-time and in-full usually carry the most weight, because they predict whether the shelf gets filled when the retailer expects it."
|
|
1448
|
+
},
|
|
1449
|
+
{
|
|
1450
|
+
"q": "What is a good supplier scorecard score?",
|
|
1451
|
+
"a": "It depends on the retailer's own threshold, and the bar is high: fill-rate and on-time targets in the high nineties are common, and falling below the line triggers fines rather than a warning. The practical read is simpler than the exact number. A score trending down is an early signal of deductions coming, and a score below the retailer's threshold means they are already posting."
|
|
1452
|
+
},
|
|
1453
|
+
{
|
|
1454
|
+
"q": "What is the Walmart supplier scorecard?",
|
|
1455
|
+
"a": "Walmart grades suppliers on OTIF, the on-time and in-full standard enforced through its fine program, visible to vendors in Retail Link. It is one example of the pattern every major retailer follows: a measured target, a penalty for missing it, and a portal where the score lives. Target and Amazon run comparable scorecards with their own metrics and thresholds."
|
|
1456
|
+
},
|
|
1457
|
+
{
|
|
1458
|
+
"q": "How do you improve a supplier scorecard?",
|
|
1459
|
+
"a": "Work the metric that carries the most weight first, usually on-time-in-full, then ASN accuracy. Most scorecard misses are not warehouse failures; they trace to a data or document gap between the ASN, the invoice, and the physical shipment. Closing that gap in the ERP and EDI setup lifts the score and cuts the deductions that follow from it at the same time."
|
|
1460
|
+
}
|
|
1461
|
+
]
|
|
1462
|
+
},
|
|
1463
|
+
{
|
|
1464
|
+
"slug": "target-vendor-chargebacks-guide",
|
|
1465
|
+
"title": "Target Vendor Chargebacks: What Each VC Code Costs",
|
|
1466
|
+
"description": "Target tracks violations, not AP codes like Walmart. What each VC violation type costs, how the VC prefix works, and how to dispute one.",
|
|
1467
|
+
"pubDate": "2026-08-21T00:00:00.000Z",
|
|
1468
|
+
"author": "Pixels and Clicks",
|
|
1469
|
+
"tags": [
|
|
1470
|
+
"Target",
|
|
1471
|
+
"Vendor Compliance",
|
|
1472
|
+
"Chargebacks",
|
|
1473
|
+
"Synergy",
|
|
1474
|
+
"OTFR",
|
|
1475
|
+
"Deduction Codes"
|
|
1476
|
+
],
|
|
1477
|
+
"readingTime": 9,
|
|
1478
|
+
"cluster": "prevention",
|
|
1479
|
+
"draft": false,
|
|
1480
|
+
"hideToc": true,
|
|
1481
|
+
"image": "/images/articles/target-vendor-chargebacks-guide-banner.jpg",
|
|
1482
|
+
"imageAlt": "Target retail vendor chargeback guide",
|
|
1483
|
+
"answer": "Target doesn't deduct by a single AP code list like Walmart. It tracks compliance violations, such as late shipping, missed fill rate, or ASN errors, and converts an unexempted one into a coded chargeback (prefix VC) after two weeks. Vendor sources disagree on the exact percentage charged, but agree on the mechanism and the Synergy dispute path.",
|
|
1484
|
+
"answerQualifier": "Compiled from five independent public vendor sources (SPS Commerce, iNymbus, Distribution Alternatives, WarehouseQuote, Productiv), August 2026. Penalty percentages conflict between sources and are flagged inline. Confirm the exact rate for your violation against your own Partners Online chargeback detail.",
|
|
1485
|
+
"faq": [
|
|
1486
|
+
{
|
|
1487
|
+
"q": "What does the VC code on a Target chargeback mean?",
|
|
1488
|
+
"a": "VC stands for Vendor Compliance, per iNymbus's deduction-prefix guide. It covers on-time shipping, pickup adherence, fill rate, and ASN availability. SPS Commerce separately describes filing a dispute \"by VC number,\" which lines up with iNymbus's table. If your remittance shows a different prefix, it likely falls under CB (invoice-match), TRT (freight), RTVS (returns), or VIAP/VONL (vendor income) instead."
|
|
1489
|
+
},
|
|
1490
|
+
{
|
|
1491
|
+
"q": "How much does a Target compliance violation cost?",
|
|
1492
|
+
"a": "Vendor sources disagree. Distribution Alternatives reports a flat 5% of cost of goods with a $150 minimum across on-time and fill-rate violations. WarehouseQuote reports a tiered structure instead: 1.5% for a general performance-adherence miss, 3% for on-time collect, on-time prepaid, and fill-rate-original violations. Confirm the rate on your own chargeback detail in Partners Online."
|
|
1493
|
+
},
|
|
1494
|
+
{
|
|
1495
|
+
"q": "What's the difference between a Target violation and a chargeback?",
|
|
1496
|
+
"a": "A violation is a system-generated flag, not yet a deduction. Per SPS Commerce, it stays open for two weeks, during which a supplier can request an exemption if the violation is invalid. If it goes unexempted through that window, it converts to a chargeback and comes off the next payment."
|
|
1497
|
+
},
|
|
1498
|
+
{
|
|
1499
|
+
"q": "How do I dispute a Target vendor chargeback?",
|
|
1500
|
+
"a": "Through the Synergy Vendor Dispute app inside the Partners Online (POL) portal, per SPS Commerce. Disputes are filed individually by VC number with supporting documentation, such as a proof of delivery, bill of lading, or screenshot. SupplyPike's help documentation separately reports a roughly 90-day dispute window for compliance chargebacks."
|
|
1501
|
+
},
|
|
1502
|
+
{
|
|
1503
|
+
"q": "How is Target's chargeback system different from Walmart's?",
|
|
1504
|
+
"a": "Walmart deducts directly against a remittance line, coded to one of a fixed set of AP codes like 22 or 25. Target's compliance program works as a two-step pipeline instead. A violation posts first, and a supplier can get it exempted. Only an unexempted violation converts into a coded chargeback. The dispute portals, the code prefixes, and even the vocabulary differ between the two retailers."
|
|
1505
|
+
}
|
|
1506
|
+
]
|
|
1507
|
+
},
|
|
1508
|
+
{
|
|
1509
|
+
"slug": "vendor-central-to-seller-central-what-changes",
|
|
1510
|
+
"title": "From Vendor Central to Seller Central: What Actually Changes",
|
|
1511
|
+
"description": "The operational shift from Amazon 1P to 3P: what changes in ordering, fees, pricing control, and margin when you move from Vendor Central to Seller Central.",
|
|
1512
|
+
"pubDate": "2026-10-18T00:00:00.000Z",
|
|
1513
|
+
"author": "Pixels and Clicks",
|
|
1514
|
+
"tags": [
|
|
1515
|
+
"Amazon 1P",
|
|
1516
|
+
"Amazon 3P",
|
|
1517
|
+
"Vendor Central",
|
|
1518
|
+
"Seller Central",
|
|
1519
|
+
"FBA",
|
|
1520
|
+
"Deductions",
|
|
1521
|
+
"Supply Chain"
|
|
1522
|
+
],
|
|
1523
|
+
"readingTime": 10,
|
|
1524
|
+
"cluster": "scoping",
|
|
1525
|
+
"draft": false,
|
|
1526
|
+
"hideToc": true,
|
|
1527
|
+
"image": "/images/articles/vendor-central-to-seller-central-what-changes-banner.jpg",
|
|
1528
|
+
"imageAlt": "Side-by-side comparison of Amazon Vendor Central and Seller Central flows showing purchase orders versus direct listings",
|
|
1529
|
+
"answer": "Moving from Vendor Central to Seller Central replaces Amazon's wholesale purchase-order model with a direct listing model. You gain pricing control and 14-day payment cycles but take on inventory risk, advertising spend, and per-unit FBA fees. Gross margin per unit is usually higher on 3P. Net margin depends on your referral rate, FBA tier, and ad spend.",
|
|
1530
|
+
"answerQualifier": "Based on Amazon's published fee schedules, Jungle Scout marketplace research, vendor community experience on r/VendorCentral, and industry reporting from SupplyKick and Mars United on Amazon's Vendor Central termination waves. October 2026.",
|
|
1531
|
+
"faq": [
|
|
1532
|
+
{
|
|
1533
|
+
"q": "Can I keep my ASINs when moving from Vendor Central to Seller Central?",
|
|
1534
|
+
"a": "Your ASINs stay. They belong to the Amazon catalog, not to your seller or vendor account. You create Seller Central offers against the same ASINs. The product detail pages, reviews, and sales rank carry over. What changes is who owns the Buy Box listing. Your 3P offer competes with every other seller on the same ASIN, including Amazon itself if they still hold inventory."
|
|
1535
|
+
},
|
|
1536
|
+
{
|
|
1537
|
+
"q": "Is selling on Amazon more profitable as 1P or 3P?",
|
|
1538
|
+
"a": "Gross margin per unit is typically higher on 3P because you set the retail price and pay a percentage referral fee instead of accepting a wholesale discount. Net margin depends on your category's referral rate, your average selling price, FBA fees per unit, advertising spend, and return rate. Low-ASP products with heavy FBA fees can net less on 3P than on 1P."
|
|
1539
|
+
},
|
|
1540
|
+
{
|
|
1541
|
+
"q": "Can I sell on both Vendor Central and Seller Central at the same time?",
|
|
1542
|
+
"a": "Yes. Many brands run a hybrid model. They keep high-volume SKUs on Vendor Central where Amazon's purchase orders provide predictable volume and list long-tail or higher-margin SKUs on Seller Central for pricing control. The risk is that Amazon's 1P offer on the same ASIN usually wins the Featured Offer, which limits your 3P sales on overlapping products."
|
|
1543
|
+
},
|
|
1544
|
+
{
|
|
1545
|
+
"q": "How long does it take to transition from Vendor Central to Seller Central?",
|
|
1546
|
+
"a": "A basic Seller Central account setup takes a few days. Building the operational infrastructure to manage listings, FBA shipments, advertising, and customer service takes 60 to 90 days for most brands. Plan for a gap period where sales volume drops while your 3P listings build ranking and advertising momentum."
|
|
1547
|
+
},
|
|
1548
|
+
{
|
|
1549
|
+
"q": "What fees does Amazon charge on Seller Central vs Vendor Central?",
|
|
1550
|
+
"a": "Seller Central charges a per-unit referral fee (typically 15% of the sale price), FBA fulfillment fees (starting at $3.65 for the smallest standard-size items), monthly storage fees, and optional advertising costs. Vendor Central takes a wholesale discount (typically 40 to 60% off retail), plus chargebacks for compliance failures, plus co-op and marketing allowances. The fee structures are completely different."
|
|
1551
|
+
}
|
|
1552
|
+
]
|
|
1553
|
+
},
|
|
1554
|
+
{
|
|
1555
|
+
"slug": "walmart-otif-fine-explained",
|
|
1556
|
+
"title": "The Walmart OTIF Fine, the 3% Rate, and What Drives a Miss",
|
|
1557
|
+
"description": "Walmart's OTIF fine is a program-level chargeback, not a per-shipment dispute. Current thresholds, how the 3% rate applies, and what drives a miss.",
|
|
1558
|
+
"pubDate": "2026-08-02T00:00:00.000Z",
|
|
1559
|
+
"author": "Pixels and Clicks",
|
|
1560
|
+
"tags": [
|
|
1561
|
+
"Walmart",
|
|
1562
|
+
"OTIF",
|
|
1563
|
+
"Retail Compliance"
|
|
1564
|
+
],
|
|
1565
|
+
"readingTime": 6,
|
|
1566
|
+
"cluster": "prevention",
|
|
1567
|
+
"draft": false,
|
|
1568
|
+
"hideToc": true,
|
|
1569
|
+
"image": "/images/articles/walmart-otif-fine-explained-banner.jpg",
|
|
1570
|
+
"imageAlt": "Hand-drawn whiteboard-style diagram explaining Walmart's OTIF fine: a delivery truck against a clock and a percentage sign labeled 3%, with a checklist equation showing on-time plus in-full compliance versus a chargeback",
|
|
1571
|
+
"answer": "Walmart's OTIF fine is a program-level chargeback: 3% of the cost of goods on cases that miss the on-time or in-full window, not a per-shipment claim like a deduction code. Since February 2024, prepaid suppliers need 90% on-time and 95% in-full, and collect suppliers need 98% collect-ready. That's down from a unified 98% requirement in place since 2020.",
|
|
1572
|
+
"answerQualifier": "Fact-checked against named trade-press reporting, not Walmart's own documentation. Walmart announced this change via the gated Retail Link portal only, with no public press release. Percentages and effective date current as of August 2026. Retailer programs change without notice.",
|
|
1573
|
+
"faq": [
|
|
1574
|
+
{
|
|
1575
|
+
"q": "Is the OTIF fine the same thing as a deduction code like Walmart code 24?",
|
|
1576
|
+
"a": "No. A deduction code like code 24 disputes a specific shipment's counted quantity. It's tied to one PO. The OTIF fine is a program-level chargeback calculated from your aggregate on-time and in-full rate across a measurement period. There's no single code number to look up on a remittance."
|
|
1577
|
+
},
|
|
1578
|
+
{
|
|
1579
|
+
"q": "Is the 3% rate applied to all of my shipments, or just the ones that miss?",
|
|
1580
|
+
"a": "Just the non-compliant cases. The 3% chargeback applies to the value of cases that missed the on-time or in-full threshold, not your total shipment value. That's part of why reported aggregate fine burden across suppliers runs far below the headline 3% rate: roughly 0.16% of cost of goods sold, per Uber Freight data cited by Forbes."
|
|
1581
|
+
},
|
|
1582
|
+
{
|
|
1583
|
+
"q": "Do prepaid and collect suppliers have the same OTIF targets?",
|
|
1584
|
+
"a": "No. Prepaid suppliers, who arrange their own freight, are held to a 90% on-time target measured against the Must Arrive By Date. Collect suppliers, where Walmart arranges freight, are measured on a 98% collect-ready standard instead. Both supplier types share the same 95% in-full target."
|
|
1585
|
+
},
|
|
1586
|
+
{
|
|
1587
|
+
"q": "Why did Walmart lower the OTIF threshold from 98% in 2024?",
|
|
1588
|
+
"a": "Walmart hasn't published its own reasoning publicly. The change was announced through the Retail Link supplier portal rather than a press release. Public reporting frames it as splitting one blended 98% target into two separate, more specific metrics, on-time and in-full, rather than a straightforward loosening of the bar."
|
|
1589
|
+
}
|
|
1590
|
+
]
|
|
1591
|
+
},
|
|
1592
|
+
{
|
|
1593
|
+
"slug": "what-is-otif",
|
|
1594
|
+
"title": "What Is OTIF? On-Time-In-Full Explained",
|
|
1595
|
+
"description": "OTIF measures whether a supplier delivered the full quantity inside the retailer's window. How retailers calculate it, and what a miss costs.",
|
|
1596
|
+
"pubDate": "2026-08-05T00:00:00.000Z",
|
|
1597
|
+
"author": "Pixels and Clicks",
|
|
1598
|
+
"tags": [
|
|
1599
|
+
"OTIF",
|
|
1600
|
+
"Retail Compliance",
|
|
1601
|
+
"CPG",
|
|
1602
|
+
"Supply Chain"
|
|
1603
|
+
],
|
|
1604
|
+
"readingTime": 9,
|
|
1605
|
+
"cluster": "prevention",
|
|
1606
|
+
"draft": false,
|
|
1607
|
+
"hideToc": true,
|
|
1608
|
+
"image": "/images/articles/what-is-otif-banner.jpg",
|
|
1609
|
+
"imageAlt": "Hand-drawn whiteboard-style diagram explaining OTIF: stacked delivery boxes labeled On Time (Schedule), In Full (Quality), and Accurate (Details), with a checklist equation showing on-time plus in-full equals OTIF success",
|
|
1610
|
+
"answer": "OTIF stands for On-Time-In-Full. It is the metric major retailers use to measure whether a supplier delivered the correct quantity (in-full) within the agreed delivery window (on-time). Walmart, Target, Kroger, and Amazon each run their own version, with penalty rates between 1% and 5% of cost of goods on non-compliant shipments.",
|
|
1611
|
+
"answerQualifier": "Based on publicly reported retailer thresholds (Forbes/Steve Banker for Walmart, vendor compliance documentation for Target, WarehouseQuote for Kroger, Front Row Group and Commerce Canal for Amazon), a McKinsey/Trading Partner Alliance out-of-stock study, and FourKites/Supply Chain Dive coverage of Kraft Heinz's OTIF improvement initiative, August 2026. Retailer programs change without notice; confirm current thresholds in your own portal.",
|
|
1612
|
+
"faq": [
|
|
1613
|
+
{
|
|
1614
|
+
"q": "What does OTIF stand for?",
|
|
1615
|
+
"a": "On-Time-In-Full. It is a compound metric: the on-time rate measures whether shipments arrived within the retailer's delivery window, and the in-full rate measures whether the shipped quantity matched the purchase order. Most retailers track and penalize these two components separately."
|
|
1616
|
+
},
|
|
1617
|
+
{
|
|
1618
|
+
"q": "What is a good OTIF score?",
|
|
1619
|
+
"a": "Above 95% is generally considered acceptable by most major retailers. Walmart requires 90% on-time and 95% in-full for prepaid suppliers. Target fines any unit outside the ship window and expects a 95% fill rate. The top quartile of CPG suppliers typically runs above 97%, according to industry benchmarks."
|
|
1620
|
+
},
|
|
1621
|
+
{
|
|
1622
|
+
"q": "Is OTIF the same as fill rate?",
|
|
1623
|
+
"a": "No. Fill rate measures only the quantity dimension: what percentage of ordered units you shipped. OTIF adds the time dimension. A shipment that arrives complete but two days late has a 100% fill rate and a 0% on-time rate. Retailers penalize both."
|
|
1624
|
+
},
|
|
1625
|
+
{
|
|
1626
|
+
"q": "How are OTIF fines calculated?",
|
|
1627
|
+
"a": "Each retailer applies a percentage of cost of goods (COGS) to non-compliant cases. Walmart charges 3% on cases that miss. Target charges 5%. Kroger starts at 1% of invoice value or $250 per order, whichever is greater. The fine applies only to the non-compliant portion, not your total shipment value."
|
|
1628
|
+
},
|
|
1629
|
+
{
|
|
1630
|
+
"q": "Do all retailers measure OTIF the same way?",
|
|
1631
|
+
"a": "No. They agree on the concept but differ on every operational detail: what counts as the delivery window, whether it's measured at the case or PO level, how the in-full threshold works, and what the penalty rate is. A supplier shipping to all four major US retailers manages four different compliance programs."
|
|
1632
|
+
}
|
|
1633
|
+
]
|
|
1634
|
+
},
|
|
1635
|
+
{
|
|
1636
|
+
"slug": "when-a-deduction-isnt-an-ops-problem",
|
|
1637
|
+
"title": "When the Deduction on Your Remittance Isn't an Ops Problem",
|
|
1638
|
+
"description": "Four deduction families trace to contracts, not operations. Three trace to your warehouse and your data. One question on a remittance line tells you which is which.",
|
|
1639
|
+
"pubDate": "2026-10-10T00:00:00.000Z",
|
|
1640
|
+
"author": "Pixels and Clicks",
|
|
1641
|
+
"tags": [
|
|
1642
|
+
"Deductions",
|
|
1643
|
+
"CPG",
|
|
1644
|
+
"Trade Promotion",
|
|
1645
|
+
"Scoping",
|
|
1646
|
+
"Chargebacks",
|
|
1647
|
+
"OTIF",
|
|
1648
|
+
"ASN",
|
|
1649
|
+
"EDI"
|
|
1650
|
+
],
|
|
1651
|
+
"readingTime": 6,
|
|
1652
|
+
"cluster": "scoping",
|
|
1653
|
+
"hub": "deduction-management-for-cpg-suppliers",
|
|
1654
|
+
"draft": false,
|
|
1655
|
+
"hideToc": true,
|
|
1656
|
+
"image": "/images/articles/when-a-deduction-isnt-an-ops-problem-banner.jpg",
|
|
1657
|
+
"imageAlt": "Stick figure at a fork in the road holding a remittance printout, left path labeled ops problem and right path labeled contract problem",
|
|
1658
|
+
"answer": "Seven deduction families appear on a CPG remittance. Four of them, promo billback, trade-fund and MDF, price-protection and holdback, and slotting and co-op, trace to a contract your sales team signed. Three of them, OTIF and compliance, ASN and shortage, and EDI and data-integrity, trace to your warehouse, your shipping data, or your EDI configuration. The sorting question is whether the deduction references a compliance scorecard or a contractual clause.",
|
|
1659
|
+
"answerQualifier": "Based on McKinsey and Forrester research on CPG trade-promotion spending, retailer compliance documentation from Walmart, Amazon, Kroger, and Target, and published deduction-resolution practitioner guidance. October 2026.",
|
|
1660
|
+
"faq": [
|
|
1661
|
+
{
|
|
1662
|
+
"q": "How do I tell whether a deduction on my remittance is a contract problem or an operations problem?",
|
|
1663
|
+
"a": "Pull the reason code and the backing document from the remittance line. If the code references a promo fund, an MDF agreement, a price-protection clause, or a slotting fee, the deduction traces to a contract your sales or trade-marketing team negotiated. If it references an OTIF scorecard, an ASN discrepancy, a shortage count, or an EDI rejection, it traces to your warehouse or your data. The first group needs a trade-promotion auditor or a broker. The second group needs an operational diagnostic."
|
|
1664
|
+
},
|
|
1665
|
+
{
|
|
1666
|
+
"q": "What deduction types does a diagnostic firm like Pixels and Clicks not cover?",
|
|
1667
|
+
"a": "Pixels and Clicks does not diagnose promo billback, trade-fund or MDF deductions, price-protection or holdback chargebacks, or slotting and co-op fees. All four trace to a contract, not to a shipping or data failure. The specialists for those are trade-promotion management firms, broker reconciliation teams, and pricing-dispute counsel."
|
|
1668
|
+
},
|
|
1669
|
+
{
|
|
1670
|
+
"q": "What percentage of CPG revenue goes to trade-promotion deductions?",
|
|
1671
|
+
"a": "CPG manufacturers spend roughly 20 percent of gross revenue on trade promotion, per McKinsey and Forrester research, with some categories running as high as 25 percent. The bulk of that spend flows through promo billback and trade-fund mechanisms, which are contract-driven and outside the scope of an operational deduction diagnostic."
|
|
1672
|
+
},
|
|
1673
|
+
{
|
|
1674
|
+
"q": "What deduction types trace to warehouse or shipping data problems?",
|
|
1675
|
+
"a": "Three families trace to operations. OTIF and compliance deductions come from missed delivery windows or failed scorecard thresholds. ASN and shortage deductions come from what the retailer counted versus what your ASN declared. EDI and data-integrity deductions come from rejected or mismatched electronic documents like the 856, 810, or 997. All three are diagnosable from your own shipping records, ASN logs, and EDI transaction history."
|
|
1676
|
+
},
|
|
1677
|
+
{
|
|
1678
|
+
"q": "Should I hire one firm to handle all my retail deductions?",
|
|
1679
|
+
"a": "Probably not. Contract-driven deductions require access to the trade-promotion agreement and the broker's records. Operational deductions require access to your warehouse management system, your EDI logs, and the retailer's compliance scorecard. The skill sets, the data sources, and the resolution paths are different. Hiring one firm for both usually means one side gets the B team."
|
|
1680
|
+
}
|
|
1681
|
+
]
|
|
1682
|
+
},
|
|
1683
|
+
{
|
|
1684
|
+
"slug": "why-growing-with-walmart-shrinks-margin",
|
|
1685
|
+
"title": "Why Growing With Walmart Can Shrink Your Margin",
|
|
1686
|
+
"description": "The price on your Walmart PO is gross, not net. Trade promotions, deductions, fees, and a 68-day cash gap can turn rising sales into a shrinking margin, and some accounts into a loss.",
|
|
1687
|
+
"pubDate": "2026-11-04T00:00:00.000Z",
|
|
1688
|
+
"author": "Pixels and Clicks",
|
|
1689
|
+
"tags": [
|
|
1690
|
+
"Margin",
|
|
1691
|
+
"Trade Spend",
|
|
1692
|
+
"Gross to Net",
|
|
1693
|
+
"Walmart",
|
|
1694
|
+
"Deductions",
|
|
1695
|
+
"Working Capital",
|
|
1696
|
+
"Research"
|
|
1697
|
+
],
|
|
1698
|
+
"readingTime": 9,
|
|
1699
|
+
"cluster": "scoping",
|
|
1700
|
+
"hub": "deduction-management-for-cpg-suppliers",
|
|
1701
|
+
"draft": false,
|
|
1702
|
+
"hideToc": true,
|
|
1703
|
+
"image": "/images/articles/why-growing-with-walmart-shrinks-margin-banner.jpg",
|
|
1704
|
+
"imageAlt": "Hand-drawn whiteboard diagram of a Walmart dollar shrinking through trade spend, deductions, fees, and a cash gap into net margin",
|
|
1705
|
+
"answer": "Growing with Walmart can shrink your margin because the purchase order price is gross, not net. Trade promotions, deductions and compliance fines, fees, and a long cash gap each take a cut before the money reaches your bank. Scale them far enough and an account can grow while it loses money.",
|
|
1706
|
+
"answerQualifier": "Based on Pixels and Clicks analysis of SEC 10-K filings, a Nielsen trade-promotion review reported by FoodNavigator, and Pixels and Clicks research pages. November 2026.",
|
|
1707
|
+
"faq": [
|
|
1708
|
+
{
|
|
1709
|
+
"q": "What is the gross-to-net gap for CPG brands?",
|
|
1710
|
+
"a": "The gross-to-net gap is the difference between a product's list or PO price and the revenue a brand keeps. Trade promotions, retailer deductions and compliance fines, contractual fees, and the cash tied up before a retailer pays each reduce the gross number. On a CPG income statement, the result is reported as net sales."
|
|
1711
|
+
},
|
|
1712
|
+
{
|
|
1713
|
+
"q": "Why does revenue grow faster than profit at a CPG brand?",
|
|
1714
|
+
"a": "Revenue often grows faster than profit because the cuts between gross and net scale with volume. More units mean more trade spend funded, more shipments exposed to deductions and OTIF fines, and more cash tied up waiting for payment. A bigger retail account multiplies all three at once, so net margin can stay flat while gross sales climb."
|
|
1715
|
+
},
|
|
1716
|
+
{
|
|
1717
|
+
"q": "Why do most trade promotions lose money?",
|
|
1718
|
+
"a": "In a review of 39 million US promotional events, almost three-quarters did not break even, per Nielsen as reported by FoodNavigator. A promotion that costs more in discount and funding than it returns in extra units is a loss. Run enough of them through one account and its growth can stop paying for itself."
|
|
1719
|
+
},
|
|
1720
|
+
{
|
|
1721
|
+
"q": "What is a negative run rate on a retail account?",
|
|
1722
|
+
"a": "A negative run rate is when extra volume through an account adds revenue but subtracts margin. Each incremental promoted case carries the full stack of trade spend, deductions, fees, and cash carry. Past a point, the next case clears less than it costs, so the account grows and loses money at the same time."
|
|
1723
|
+
},
|
|
1724
|
+
{
|
|
1725
|
+
"q": "Which part of the gross-to-net gap can a supplier recover?",
|
|
1726
|
+
"a": "Trade terms, fees, and payment days move only when a supplier renegotiates with the buyer. Disputed deductions are the exception. A deduction a retailer took in error is cash it already holds, and each one traces to a cause in the ASN, the invoice, or the item file. Those are recoverable without changing the contract."
|
|
1727
|
+
}
|
|
1728
|
+
]
|
|
1729
|
+
},
|
|
1730
|
+
{
|
|
1731
|
+
"slug": "wrong-upc-after-erp-migration-shortage-claim",
|
|
1732
|
+
"title": "Why Amazon Deducts After Your ERP Migration",
|
|
1733
|
+
"description": "Two weeks after ERP go-live, Amazon deducts on shipments you sent complete. The cases scanned fine. The unit UPCs did not. What broke, and how to catch it.",
|
|
1734
|
+
"pubDate": "2026-09-28T00:00:00.000Z",
|
|
1735
|
+
"author": "Pixels and Clicks",
|
|
1736
|
+
"tags": [
|
|
1737
|
+
"ERP",
|
|
1738
|
+
"UPC",
|
|
1739
|
+
"GTIN",
|
|
1740
|
+
"Migration",
|
|
1741
|
+
"NetSuite",
|
|
1742
|
+
"Business Central",
|
|
1743
|
+
"Amazon 1P",
|
|
1744
|
+
"Shortage",
|
|
1745
|
+
"ASN"
|
|
1746
|
+
],
|
|
1747
|
+
"readingTime": 8,
|
|
1748
|
+
"cluster": "erp-technical",
|
|
1749
|
+
"draft": false,
|
|
1750
|
+
"hideToc": true,
|
|
1751
|
+
"image": "/images/articles/wrong-upc-after-erp-migration-shortage-claim-banner.jpg",
|
|
1752
|
+
"imageAlt": "The four item-master barcode fields a NetSuite or Business Central migration can map wrong: primary UPC, additional barcode, item alias GTIN, and unit-of-measure item reference",
|
|
1753
|
+
"answer": "After an ERP migration, your cases can ship with the correct case label but the wrong unit-level UPC. Amazon's fulfillment center scans the unit. If the scan resolves to a different item than your ASN declared, Amazon posts a shortage on your ASIN and an overage on the mystery item. The remittance signature: a matched shortage and overage on the same PO.",
|
|
1754
|
+
"answerQualifier": "Based on Oracle NetSuite's own help documentation (UPC Code field, item aliases, GTIN 01 identifier), Microsoft Learn's Business Central item-reference documentation, public GS1 and Amazon barcode-requirement guidance, and a pattern that supplier operators have described publicly on r/VendorCentral (linked in the piece). September 2026.",
|
|
1755
|
+
"faq": [
|
|
1756
|
+
{
|
|
1757
|
+
"q": "Why does a shortage claim show up when the shipment left complete?",
|
|
1758
|
+
"a": "Amazon's fulfillment center scans at the unit level, not just the case. If the case label scans to the correct ASIN but the unit label inside scans to a different real ASIN, Amazon books zero receipt on your item and an unexpected receipt on the mystery item. The first is a shortage. The second is an overage. Both hit the same PO."
|
|
1759
|
+
},
|
|
1760
|
+
{
|
|
1761
|
+
"q": "Why did our cutover UAT pass without catching a wrong UPC?",
|
|
1762
|
+
"a": "UAT test data is usually seeded with UPCs the test scripts already know are correct. Nothing in the test compares the new item master against physical labels on inventory produced under the old master. The mismatch only surfaces when Amazon scans real pre-cutover inventory against the new master's expectation of what the label should be."
|
|
1763
|
+
},
|
|
1764
|
+
{
|
|
1765
|
+
"q": "Which item-master field usually breaks in a NetSuite or Business Central migration?",
|
|
1766
|
+
"a": "The field that stores the scannable identifier at the unit of measure Amazon actually receives. In NetSuite, that is the UPC Code on the item record or a GTIN in the item aliases table. In Business Central, that is an Item Reference of type Barcode tied to the correct unit of measure. A migration that maps the each-level UPC to the case-level record, or the reverse, ships product whose labels do not match the item master."
|
|
1767
|
+
},
|
|
1768
|
+
{
|
|
1769
|
+
"q": "How do I catch this at pallet scan instead of after the deduction lands?",
|
|
1770
|
+
"a": "Before the pallet leaves the dock, scan one unit-level barcode. Look up the value in your ERP's item-reference or alias table. Compare the result against the item the ASN is about to declare for that PO. If they do not match, block the ASN. NetSuite item aliases and Business Central item references both support this lookup natively."
|
|
1771
|
+
},
|
|
1772
|
+
{
|
|
1773
|
+
"q": "How do I tell a UPC-migration failure apart from a real shortage?",
|
|
1774
|
+
"a": "A physical shortage shows up as one line: units expected, units received short. A UPC-migration failure shows up as two lines on the same PO: a shortage line for your ASIN and an unexpected-item overage line for a different ASIN at the same case count. The matched pair is the signature."
|
|
1775
|
+
}
|
|
1776
|
+
]
|
|
1777
|
+
},
|
|
1778
|
+
{
|
|
1779
|
+
"slug": "your-team-after-ai-what-agencies-miss",
|
|
1780
|
+
"title": "Your Team After AI: What Most Agencies Never Plan For",
|
|
1781
|
+
"description": "Most AI agencies sell a deployment. The harder question is what happens to your team and your workflows after the system goes live. That determines whether the project works or gets abandoned.",
|
|
1782
|
+
"pubDate": "2026-10-16T00:00:00.000Z",
|
|
1783
|
+
"author": "Pixels and Clicks",
|
|
1784
|
+
"tags": [
|
|
1785
|
+
"AI Implementation",
|
|
1786
|
+
"Change Management",
|
|
1787
|
+
"CPG",
|
|
1788
|
+
"Productivity",
|
|
1789
|
+
"Working Philosophy"
|
|
1790
|
+
],
|
|
1791
|
+
"readingTime": 8,
|
|
1792
|
+
"cluster": "scoping",
|
|
1793
|
+
"draft": false,
|
|
1794
|
+
"hideToc": true,
|
|
1795
|
+
"image": "/images/articles/your-team-after-ai-banner.jpg",
|
|
1796
|
+
"imageAlt": "Stick figure at a crossroads between unused tool and team upgrade, with a workflow chart and upward arrow",
|
|
1797
|
+
"answer": "AI implementation succeeds or fails based on what happens to your team after the system goes live. The automation has to target the real bottleneck, freed capacity has to be redeployed to higher-value work, and the team has to adopt the new workflow. Most agencies plan for the first. Almost none plan for the other two.",
|
|
1798
|
+
"answerQualifier": "Based on the working methodology of Pixels and Clicks, Gartner research on GenAI project abandonment (2024), and McKinsey data on transformation program outcomes. October 2026.",
|
|
1799
|
+
"faq": [
|
|
1800
|
+
{
|
|
1801
|
+
"q": "How does Pixels and Clicks approach AI implementation differently from other agencies?",
|
|
1802
|
+
"a": "Pixels and Clicks starts with a paid assessment that maps how work actually gets done before proposing any build. The assessment deliverable is a process map showing every step the team takes, the time each step costs, and where the gaps are between what leadership described and what operations does. The assessment also includes a go/no-go recommendation."
|
|
1803
|
+
},
|
|
1804
|
+
{
|
|
1805
|
+
"q": "Does Pixels and Clicks replace employees with AI?",
|
|
1806
|
+
"a": "Pixels and Clicks automates low-value repetitive work so existing employees can move to higher-value tasks like deduction tracing, dispute management, and root-cause analysis. Every engagement includes a redeployment plan that names the specific higher-value work and sequences it by priority."
|
|
1807
|
+
},
|
|
1808
|
+
{
|
|
1809
|
+
"q": "What are the first, second, and third order effects of AI implementation?",
|
|
1810
|
+
"a": "First order: the automated task gets faster and more accurate. Second order: the person who did that task moves to judgment-heavy work that compounds value. Third order: the organization starts questioning inefficiencies it used to accept as cost of doing business."
|
|
1811
|
+
},
|
|
1812
|
+
{
|
|
1813
|
+
"q": "Why does Pixels and Clicks run a paid assessment before building anything?",
|
|
1814
|
+
"a": "The real bottleneck rarely matches what leadership describes. Building an automation from a description of the workflow rather than mapping how the team actually works produces tools the team ignores. The assessment maps the real process and costs before any build decision. We've walked away from paid build work after an assessment showed the manual process cost less than the automation would."
|
|
1815
|
+
},
|
|
1816
|
+
{
|
|
1817
|
+
"q": "What does change management look like in a Pixels and Clicks engagement?",
|
|
1818
|
+
"a": "Every automated workflow gets a named owner inside the company, picked during the build. The workflow ships with a one-page runbook covering what the system does, what it replaced, what to check when something looks wrong, and who to call. Walkthroughs are live calls. Training runs alongside the build."
|
|
1819
|
+
}
|
|
1820
|
+
]
|
|
1821
|
+
}
|
|
1822
|
+
]
|