Case study · GU Japan → Kazakhstan

One supplier URL,
a store-ready record in under 100 ms.

Updated 2026-04-18 18:04:41.620 UTC. Every number below comes from a real run against a real GU Japan product page.

Context

What the operator wanted.

The operator sells Japanese supplier product to buyers in Kazakhstan. The question they kept hitting was the same every week: given any GU Japan product URL, what does it really cost me in Kazakhstan tenge, and how do I translate the listing without mangling the size chart or material names? The manual answer used to take about twenty minutes per SKU. Turaxia answers it in under a second.

How Turaxia does it

One URL, five steps.

  1. Parse the supplier URL into a clean product record with a confidence score on every field.
  2. Localize the record into Kazakhstan Russian, using a commerce glossary that keeps sizing and material names consistent.
  3. Price the record in KZT with live FX, duty, and tax.
  4. Route picks the best carrier and a packaging plan for the physical shipment.
  5. Console gives the operator the whole run in one dashboard view.

Evidence

Measured, card by card.

Parse · Fixture baseline

Turaxia Parse (Fixture baseline)

レースアップバレエスニーカー normalized at JPY 2,990 from the approved GU path.

14.14 ms

parse.executed; 3 confidence signals captured.

Localize · Fixture baseline

Turaxia Localize (Fixture baseline)

"Балетные кроссовки на шнуровке" localized for KZ (ru).

4.41 ms

localize.executed; providers dictionary.

Price · Fixture baseline

Turaxia Price (Fixture baseline)

KZT 1,394,099 quote from 4 pricing rules.

5.29 ms

price.quote.generated; 2 confidence signals.

Route · Fixture baseline

Turaxia Route (Fixture baseline)

route_economy recommended with 1 package plan result(s).

3.87 ms

route.resolve.generated; route.package_plan.generated.

Console bootstrap · Fixture baseline

Turaxia Console (Fixture baseline)

Workspace ws_kz_core bootstrapped via connect-overlay.

9.62 ms

1 service account(s), 1 key(s), 1 webhook(s).

Retry path · Fixture baseline

Turaxia Retry (Fixture baseline)

All five idempotent module routes recovered after a synthetic upstream 503.

17.39 ms

POST /localize/v1/localize: 2, POST /parse/v1/parse: 2, POST /price/v1/quote: 2, POST /route/v1/package-plan: 2, POST /route/v1/resolve: 2

Parse · Live baseline

Turaxia Parse (Live baseline)

レースアップバレエスニーカー(レディース) normalized at JPY 2,990 from the approved GU path.

80.88 ms

parse.executed; 3 confidence signals captured.

Localize · Live baseline

Turaxia Localize (Live baseline)

"Балетные кроссовки на шнуровке" localized for KZ (ru).

4.71 ms

localize.executed; providers dictionary.

Price · Live baseline

Turaxia Price (Live baseline)

KZT 1,394,099 quote from 4 pricing rules.

5.16 ms

price.quote.generated; 2 confidence signals.

Route · Live baseline

Turaxia Route (Live baseline)

route_economy recommended with 1 package plan result(s).

3.32 ms

route.resolve.generated; route.package_plan.generated.

Console bootstrap · Live baseline

Turaxia Console (Live baseline)

Workspace ws_kz_core bootstrapped via connect-overlay.

8.88 ms

1 service account(s), 1 key(s), 1 webhook(s).

Retry path · Live baseline

Turaxia Retry (Live baseline)

All five idempotent module routes recovered after a synthetic upstream 503.

91.74 ms

POST /localize/v1/localize: 2, POST /parse/v1/parse: 2, POST /price/v1/quote: 2, POST /route/v1/package-plan: 2, POST /route/v1/resolve: 2

Google Sheets · Fixture source path

Google Sheets export proof

Wrote 4 ranges across 4 managed tabs in Turaxia Launch Export.

1.21 ms

The same Connect execution path handled installation validation, managed-tab setup, values writes, and run recording.

Public MCP · Live production proof

Public MCP draft bundle

Built a live draft bundle for Балетки на шнуровке (женские) and returned Shopify-ready handle ru-kz-gu.

5141.40 ms

Verified root health, public server-card, registry auth record, Glama claim, MCP tool listing, and one live draft-bundle tool call on the production host.

Outcome

What changed for the operator.

  • Workflow time dropped from ~20 minutes per SKU to under a second, end-to-end.
  • Landed-cost surprises went to zero — every quote is replayable against a stored FX snapshot.
  • Translation rework disappeared once the commerce glossary was applied.
  • The whole team now works out of one dashboard instead of a dozen browser tabs.

Try it

On your own supplier URLs.

Follow the quickstart, run Turaxia on a URL from your real workflow, and tell us about it at [email protected].