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 321–360 of 651 in this first collection.
Troubleshooting guide
BigCommerce order webhooks: how they fail, retry and get deactivated
The answer rules, the retry schedule and the deactivation conditions behind BigCommerce webhooks, and how to find the orders a deactivated one missed.
Platform
BigCommerce order notifications and shipping setup: what the store promises and what your systems must do
Understand how BigCommerce tells other systems about orders, how its shipping zones and carrier connections are organised, and where a quiet failure hides.
Platform
Magento and Adobe Commerce: indexers, cron and product exports as operational risks
Understand why Magento storefronts can lag behind the admin, what the scheduled jobs must do, and what a catalogue export contains when you move away.
Buyer collection
For a store operator without a developer: describe the fault so it can be fixed on a copy
How to say where an order, payment, shipping or stock fault stops, what to send first, and how to choose between a single fix, a standing check and a recovery project.
Buyer collection
For a store owner moving platforms: move the catalogue without trusting a bare import
What to decide and prepare before moving a product catalogue to Shopify, how to prove it on a test store, and what stays your job.
Collection
Store checkout and order faults: work along the buying journey to find the first broken link
A diagnosis order for an online store that loses orders or money: product choice, shipping, discount, payment confirmation, renewals, emails and downstream sync, with the paid route for each.
Collection
Store catalogue and stock integrity: import, structure, stock sync and platform move in order
A diagnosis order for product data and stock problems: bulk import damage, variant structure, stale storefronts, stock drift and catalogue moves, with the paid route for each.
Inspectable example
Synthetic CSV encoding fixture: a byte-order mark, accents and the wrong reading side by side
An invented four-line CSV with a leading byte-order mark and accented, currency and trademark characters, with the bytes, the wrong readings and the expected values an importer test should assert.
Inspectable example
Synthetic CSV quoting matrix: commas, doubled quotes, line breaks, semicolons and an unclosed quote
An invented supplier CSV read two ways, by splitting at commas and with a real CSV reader, with the record and line counts, a semicolon file read with the wrong delimiter and an unclosed quote.
Inspectable example
Synthetic XML feed cases: five first errors a parser reports and one well-formed file that loses fields
Invented XML snippets with the first error a standard parser reports for each, plus a well-formed namespaced item with CDATA that a text-matching importer misreads.
Inspectable example
Synthetic feed comparison: eight products, planted changes, formatting noise and a counts check
Two invented supplier file versions with a reordered file, formatting-only differences and six real differences (three changed, two added, one absent), and the key-based report and reconciliation an acceptance test should expect.
Inspectable example
Synthetic image-link fixture: eight cases an image check must classify, and what each does to a product
An invented fixture of eight image-address outcomes with the status, declared type, recorded class and the action under a hold-for-review rule, plus four destinations the check must refuse, as an acceptance matrix for an import image check.
Troubleshooting guide
Supplier CSV shows é instead of é, or the first column goes missing: check the encoding and byte-order mark
Why accented letters turn into character pairs and why an invisible first character breaks the first header name, how to tell which one you have, and what a safe fix looks like.
Troubleshooting guide
A comma in a product description pushes the price into the wrong column: read quoted fields properly
Why only some supplier CSV rows shift, how quotes, doubled quotes and line breaks inside fields should be read, why semicolon files break a comma reader, and how to prove the row count.
Troubleshooting guide
A supplier XML feed stops with a parse error: find the first error before blaming your importer
What well-formed XML requires, why a conforming parser stops instead of skipping a bad item, the usual first errors in a feed, and how to separate a supplier fault from an importer fault.
Troubleshooting guide
A nightly SFTP fetch imports half a file, repeats a file or stops after the supplier's server changes
How to tell a finished supplier file from one still uploading, stop the same file being imported twice, and treat a changed server host key as a stop sign rather than an error to switch off.
Troubleshooting guide
A scheduled supplier fetch runs at the wrong time, twice or not at all: time zones, clock changes and cron surprises
Why a cron-style schedule can fire an hour off, skip or repeat around clock changes, run on the wrong days, or break on a percent sign, and how to make the job safe whichever happens.
Troubleshooting guide
Comparing two supplier feed versions: match products by key, not by line, and make the counts add up
Why a text comparison of two supplier files buries real changes, how a key-based comparison reports added, absent and changed products, and the arithmetic that proves nothing was missed.
Troubleshooting guide
Converting an ERP export for a store import: decimal commas, day-first dates, codes and rejects
Why hand-editing an ERP export produces different files on different days, and how explicit number, date and code rules, exact decimal arithmetic and a reject file make the conversion repeatable.
Troubleshooting guide
Supplier categories end up in Uncategorised: use a mapping table with an unmapped list, not loose matching
How to map a supplier's category names to your store categories with one reviewed row per value, an explicit unmapped state, exact matching and a report of new or changed values.
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.
Inspectable example
Synthetic price list: a page-by-page row count that finds two mistakes a matching total hides
An invented three-page price list shows why rows are counted per page. A first extraction matches on the total, 14 of 14, while page 1 is a row short and page 2 has an extra row.
Inspectable example
Synthetic merged-cell report flattened: nine rows in, five records out, every total reconciled
An invented printed-style sales report with merged region labels, subtotal rows and a spacer becomes a flat five-record table, with a reconciliation showing 9 original rows = 5 records + 4 removed.
Inspectable example
Synthetic quotation: why the same three lines total 4.38 or 4.39 depending on the rounding rule
Three invented lines of 1.30 plus a 12.5 per cent add-on give 4.38 if the add-on is rounded per line and 4.39 if it is rounded on the total. The rule must be written down.
Inspectable example
Synthetic rename manifest: three clean renames with matching checksums and four held names
An invented seven-file folder shows a dry run and a manifest with a row for every file, with three renamed files whose checksums match, and four held, a pair of names that differ only in letter case, a reserved device name and a name ending in a period, all listed, not guessed.
Inspectable example
Synthetic date column: which rows a rule can settle, and which must stay on the ambiguity list
Nine invented entries show day-first and month-first typing, a two-digit year, a row where only one reading is possible, an impossible date and a four-year shift, with the decision and reason for each.
Platform
PDF documents: getting data, forms and searchable text out of office files
For office managers and administrators with PDF price lists, filled forms and scans: how to tell which kind of PDF you have, how to check what is extracted and where a paid, checked job fits.
Platform
Microsoft Excel workbooks: repair, tidy and make them reliable
For administrators and small businesses who rely on Excel: where workbooks go wrong, the order to diagnose them in, and the checked, fixed-scope jobs that repair formulas, flatten layouts and clean dates and duplicates.