Shopify shipping migration auditor

Will your Shopify app survive market-driven shipping?

Merchant-owned shipping is moving from DeliveryProfile to Markets. Legacy reads can become stale and writes can succeed without changing live settings. Find those paths before rollout.

Private by design Report in seconds File + line evidence
shipping.ts84
mutation UpdateRates {
  deliveryProfileUpdate(
    id: $profileId
    profile: $input
  ) {
    userErrors { message }
  }
}
HIGH RISK

Mutation success may not update live merchant shipping.

Use an app-owned profile or Markets API →
NowFeature previewTest in a development store
Oct 1, 2026Merchant rolloutCompatibility warnings begin
Jul 1, 2027Full migrationAll merchants on the new model
Browser-local repository audit

Find the code paths that can silently stop working.

Scan JavaScript, TypeScript, GraphQL, Ruby, PHP, TOML, YAML, and JSON. MarketReady flags legacy merchant-profile calls, missing scopes, old API versions, and absent rollout branches.

  • Source code never leaves your browser
  • File and line-level evidence
  • Migration path suggestions

Drop a ZIP here

Up to 25 MB. Generated and dependency folders are skipped.

orNothing is uploaded. No login, token, or Shopify access required.
What the scanner checks

A migration report developers can act on.

MarketReady uses transparent, versioned rules sourced from Shopify’s upgrade guide. It does not send code to an LLM or claim certainty where static analysis cannot know profile ownership.

01

Legacy API inventory

Find all eight affected DeliveryProfile fields and mutations with file names, line numbers, and matching code.

02

Silent failure patterns

Flag write paths that can report success while leaving a migrated merchant’s live configuration unchanged.

03

Scopes and branching

Check for read_markets, write_markets, read_product_listings, and ShopFeatures.marketDrivenShipping.

04

Upgrade path

Choose among app-owned profiles, Contextual Product Feeds, Markets reads, and Markets writes.

Privacy architecture

Your source code stays on your machine.

The ZIP is decompressed in browser memory. Only short matching lines are placed in a report stored in localStorage. There is no upload endpoint, repository token, database, or analytics payload containing source.

Your ZIP→Browser memory→Local report
Before October 1

Find the risky path. Test the right replacement.

Run the scanner