Aily Kang
한국어

Menu

← All case studies
2026.05–09Professional work

Commerce data operations — verify what changes and what must stay intact

PythonSQLCafe24 APIPlaywrightPyInstaller

Evidence151 products / 268 rows repaired; zero residual mismatches

Context

For an office-furniture retailer, I owned product, option and price reconciliation alongside new storefront development. After the initial migration, I continued tracing and correcting inconsistencies in live sales data.

Problem

Values diverged across channels. Some products appeared in autocomplete but disappeared from search results: the two features read different copies of the data, so checking only the master missed the fault.

Decisions

Trace the data actually used by the page

I confirmed that autocomplete and search read different tables, then compared code, name, model, visibility and inventory classification across the catalogue. The repair scope was 268 rows covering 151 products.

Define the values that must remain unchanged

I prepared a change plan and backup, with updates conditional on both the original and master values. On MyISAM, I retained backup hashes and conditional recovery SQL instead of assuming transaction rollback.

Read again after a successful write

An independent database session confirmed zero remaining mismatches in the five audited fields on 7 September. I also checked protected price, option and mapping hashes, the actual price-sync reader and nine public searches.

Keep cosmetic differences distinct from operational errors

On 5 September, I audited 603 products in each of two Cafe24 stores. Core price, code, source-provided option, shipping and sales-state checks matched. Three whitespace-only name differences were recorded separately.

What I owned

  • Data analysis
  • Diagnostic and repair pipelines
  • Backup and conditional recovery
  • Independent requery and public-page verification
  • Operator-facing packaging

Actual deliverables

  • Requery audit of 603 products in each of two Cafe24 stores (5 Sep 2026)
  • Repair and independent verification of 268 search/display rows for 151 products (7 Sep 2026)
  • Change plan, backup hashes, conditional recovery SQL and public search checks

Scope and verification

151 products / 268 rows repaired; zero residual mismatches

Figures describe the audits on 5 and 7 September 2026. The search repair did not change prices or send new prices to external channels. Client identities, product data and internal admin screens are withheld.

If you need this kind of work

Describe the thing you're currently stuck on. I'll reply by first separating what I can take on from what I can't.

kjyhopekr@gmail.com

More in this field