Find the outcome you need.
Start with a symptom, a platform or the thing you want working.
With JavaScript, search filters the whole collection in your browser. Without it, use the linked pages and section navigation below; query filters need JavaScript.
Showing entries 81–112 of 112 in this first collection.
Troubleshooting guide
Supplier image links that load a page, redirect in circles or time out: classify them before import
How to tell a working image address from a missing file, a redirect, an error page returned as success, a wrong file type or a slow host, and how to check them without stalling the import.
Troubleshooting guide
Merchant Center cannot process your product file? Check the format, header row and XML layout
The file-level rules that make Merchant Center reject or misread a product file, from accepted formats, header row, tabs and line breaks, encoding, XML namespace and tag case, extensions and compression.
Troubleshooting guide
Merchant Center scheduled fetch fails or shows an old file? Check the address, access and what comes back
Why a scheduled fetch of your product file fails or stays stale: an address that leads to a page, redirects, blocks or permissions, login handling, compression, size and the difference between a fetch and an SFTP upload.
Troubleshooting guide
Merchant Center says your price does not match the page: compare feed, page, checkout and markup
What Google compares when it flags an inaccurate price, the causes in order of likelihood, tax and format rules that cause mismatches, and how fixing and review work after you correct the data.
Troubleshooting guide
Merchant Center flags availability: pre-orders, sold-out lines, variants and a feed that refreshes too slowly
The availability values and situations that Merchant Center flags, why a daily fetch cannot follow fast stock changes, and which fixes belong in the feed, the page or the refresh route.
Troubleshooting guide
Merchant Center rejects product images: file type, size, URL rules, robots access and overlays
What Google's image_link attribute requires and why images are disapproved: the extension must match the real format, the size minimum, URL and robots rules, stable addresses and disallowed content.
Platform
CSV supplier files: find the first failing layer before changing the importer
For distributors and merchants who import product, stock and price data from CSV: a map of the layers a file passes through, where each fault shows up and which guide or job fits.
Platform
XML product feeds: well-formed first, then namespaces, then meaning
For distributors and merchants who receive or send product data as XML: why a broken file stops everything, where namespaces and escaping cause quiet loss, and which guide or job fits.
Platform
Google Merchant Center product data: fix the file, then the items, then the images
For merchants whose Shopping products are warned or disapproved: the order in which to diagnose file, price, availability and image problems, and where a data fix ends and Google's review begins.
Buyer collection
For an operations manager: make supplier files arrive complete, readable and only once
A page for the person who owns how supplier files are fetched, decoded and imported: what to document, how to describe a failure and which small fixed job or standing check fits.
Buyer collection
For a merchant with flagged Shopping products: find the cause group before you edit the feed
A page for the person who owns the Merchant Center data source: what to collect, how to sort flagged products by cause and which fixed job, project or monthly watch fits.
Collection
Supplier file import goes wrong: work through delivery, bytes, structure and release in order
An ordered process map for a supplier file that imports wrongly: confirm the file arrived whole, then decode it, then read its rows and fields, then check its layout, meaning, mapping and images, then compare before release.
Collection
Merchant Center products flagged: work through account, file, price, stock, images and review in order
An ordered process map for flagged Shopping products: separate account-level issues from item issues, then fix file fetch and format, price and availability, images and identifiers, then plan the refresh route and review.
Free tool
CSV header diff: find missing, added, renamed and duplicate columns between two files
Paste two CSV header rows, or read the header of two small files in your browser, and see missing, added and likely renamed columns, duplicate and empty headers and the delimiter. Nothing is uploaded.
Free tool
Pack and case unit-price calculator: compare supplier prices per single unit
Enter supplier price lines priced per unit, pack or case. Get the exact price per single unit, the working, and the lines whose pack basis is unclear. No floating point.
Troubleshooting guide
Members-only pages on Wix, Squarespace and Webflow: what each builder's own tools can and cannot do
Wix and Squarespace each have a built-in members feature with different rules. Webflow no longer has one. This guide sets out how each works and the limits worth knowing before you promise anyone privacy.
Platform
Webflow sites: what the builder handles, where its documented limits are and which bounded jobs fit
Webflow hosts the site, the CMS and the forms. This page sets out what that covers, the documented limits that catch owners out, and the bounded repairs and builds that fit.
Inspectable example
Synthetic example: a members-only access matrix with one leak that only appears from the cache
An invented test grid for a made-up course site, showing expected and actual access and the cached sequence that exposes a fault.
Troubleshooting guide
Members-only WordPress content visible to the wrong people: check caching, roles and the other routes
Why access rules can pass in the admin and still fail in practice: page caches, role changes that do not apply, and routes such as the REST data interface.
Inspectable example
Synthetic supplier-key matrix: zeros, long codes, reused SKUs and an unmapped item
Four invented product mappings expose numeric coercion and cross-supplier collisions; an unknown key stays unassigned instead of becoming a guessed product.
Inspectable example
Synthetic supplier-update contract: blank price, absent field and missing product
A worked decision matrix separates a field omitted from a partial update from a product absent from a complete snapshot, with explicit hold and no-change results.
Inspectable example
Worked pack-price example: why 36 items cost 59.97, not the rounded display total
An invented USD 19.99 pack of 12 distinguishes the purchase basis from a rounded per-item comparison and shows exactly where a misleading total arises.
Inspectable example
Synthetic feed-disposition sequence: newer, late, repeated and conflicting updates
Starting at supplier version 41, a six-step expected-state sequence shows when a feed changes the accepted version and when the previous state must remain intact.
Troubleshooting guide
Supplier SKUs lose leading zeros: preserve the identifier before importing
Keep supplier identifiers textual and compare exact keys before a stock or price feed creates a second product or updates the wrong one.
Troubleshooting guide
Two suppliers use the same SKU: match the supplier and code together
Prevent one supplier's stock or price from landing on another supplier's item, and keep unapproved cross-supplier mappings out of an automatic update.
Troubleshooting guide
A supplier feed repeats one key with different prices: reject the conflict before updating
Distinguish an identical duplicate from conflicting rows and choose a documented disposition instead of allowing file order to decide a business value.
Troubleshooting guide
Blank supplier price clears a good value: distinguish unchanged, empty and explicit removal
Give missing fields and blank cells different update meanings before a partial supplier feed erases a price or silently substitutes zero.
Troubleshooting guide
An item disappears from a supplier feed: is it a full snapshot or just a delta?
Do not turn an omitted SKU into zero stock or discontinued status until the source defines completeness, coverage and deletion semantics.
Troubleshooting guide
Supplier quotes per pack, your app compares per item: make the units explicit
Keep pack size, stock units and price basis separate so an apparently cheaper supplier is not selected using incomparable values or rounded display prices.
Troubleshooting guide
Yesterday's supplier feed finishes last: keep older data from replacing a newer version
Compare source-issued versions at the publication boundary and distinguish a late old feed from an authorised correction to the current one.
Troubleshooting guide
Supplier adds a CSV column: reject header drift before fields shift into the wrong place
Validate the declared header and every row's shape before mapping a supplier stock or price update, rather than accepting a successfully parsed but misaligned record.
Collection
Supplier stock and price import checks: choose the first failing boundary
A distributor-focused sequence from CSV shape through identity, field meaning, units and feed publication, linked to worked synthetic cases and narrowly eligible paid enquiries.