New

StoreProof is in public beta — evidence-first storefront QA for Shopify

Run an audit

Independent, founder-led commerce software studio

We buildsoftware forthe work behindcommerce.

RXR Code builds focused products, open-source tools, and selective client systems for storefront quality, product operations, integrations, and automation.

See StoreProof

Select a node or layer to trace the system.

Where commerce gets fragile

Bring the part that should work better.

RXR Code focuses on the work that becomes expensive when it stays manual, difficult to verify, or split across systems.

01

Storefront problems reach customers first.

Buying-flow, mobile, accessibility, and technical issues are difficult to catch consistently before they affect a real visit.

02

Product launches lose their supporting content.

A product can become active while the related article, education, or launch content remains an unfinished task.

03

Commerce systems drift out of sync.

Catalog, customer, order, and operational data still move through manual copy-paste and fragile handoffs.

04

Repeated work stays invisible.

Important tasks live in inboxes, spreadsheets, or memory instead of a workflow the team can review and recover.

Products with honest status

Start with what is real today.

StoreProof is in public beta. CatalogCue remains in private development. Shopify Fixtures and Catalog Parity are public, MIT-licensed tools available on GitHub and npm.

Storefront qualityPublic beta

StoreProof

Catch storefront problems before they become customer problems.

StoreProof runs a real browser through Shopify storefronts, distinguishes confirmed findings from scanner limitations, signs eligible same-origin storefront requests with Web Bot Auth, and returns evidence teams can review and verify.

Public betaReal-browser auditsShareable reports
Run a storefront audit
StoreProof storefront audit result showing audit coverage and prioritized storefront checks
Real browser evidenceInspect → verify → act
CATALOGCUE / SHOPIFY APPPRIVATE DEVELOPMENT
CatalogCue
Products

Private-development preview. Product data stays under merchant review.

Product event → review-ready draftProject status →
View CatalogCue project status
Product-to-content workflowPrivate development

CatalogCue

Turn product activity into content ready for review.

When a Shopify product is created or becomes active, CatalogCue can prepare a grounded blog draft from the product data already in Shopify. The merchant reviews the result and chooses whether to save it as an unpublished Shopify article.

Grounded in Shopify dataReview requiredNever auto-publishes
See what CatalogCue is becoming

Founder experience

Built on production commerce experience.

RXR Code is informed by Gilriel Rodriguez's hands-on experience with commerce platform migrations, ERP-connected workflows, storefront delivery, and operational tooling.

Commerce platform migrations

Experience navigating B2B storefront delivery, platform change, and the operational details that sit behind a migration.

ERP-connected operations

Experience with catalog, customer, and order data crossing the boundaries between commerce and business systems.

Storefront delivery and QA

Experience shipping customer-facing commerce work and protecting quality after the storefront goes live.

This experience was gained through the founder's professional work and is not presented as RXR Code client work.

View Gilriel's engineering work

Selective client engineering

When the problem is specific, build around the workflow.

RXR Code takes on focused client work when a storefront, internal process, integration, or repeated handoff needs a purpose-built system.

Storefronts

Build or rebuild the storefront around how the business actually sells, merchandises, and converts. This covers the customer-facing layer where speed, clarity, and day-to-day operation need to work together.

Typical outcomes

  • Theme implementation
  • Conversion-focused UX
  • Migration and cleanup
  • Operational storefront features
BuildsRebuildsB2B

When to bring RXR Code in

Bring the part that does not fit cleanly off the shelf.

A storefront needs a rebuild.A workflow needs its own interface.Two systems need to exchange data reliably.Manual work needs to become visible and repeatable.
Developer infrastructureOpen source

Shopify Fixtures

Reproducible development data for Shopify.

An open-source CLI for generating, versioning, validating, and safely applying supported Shopify development-store fixtures.

Public repositoryMIT licensedPublished on npm
shopify-fixtures — zsh — 92×24

rxr@commerce ~/shopify-fixtures % npx @rxrcode/shopify-fixtures@next generate --products 5 --collections 2 --seed 42

✓ fixtures generated

rxr@commerce ~/shopify-fixtures % npx @rxrcode/shopify-fixtures@next push

PLANSKIP    productCREATE  collectionUPSERT  metaobjectPlan only. Run with --apply to write.

rxr@commerce ~/shopify-fixtures %

GenerateValidatePlanApply
catalog-parity — zsh — 92×24

rxr@commerce ~/migration % npx @rxrcode/catalog-parity@0.1.1 compare source.csv target.csv --key sku --field title --field price

✗ Catalog differences found

Source 3 · Target 3 · Matched 2 · Missing 1 · Extra 1 · Changed fields 1

CHANGED MUG-WHT price        source: "18.50"        target: "19.00"MISSING TOTE-NAT not found in targetEXTRA    CAP-NVY only in target

rxr@commerce ~/migration %

ExportCompareReview
Catalog verificationOpen source

Catalog Parity

Compare commerce catalogs before migrations go live.

An offline, platform-neutral CLI for finding missing records, unexpected target records, and field-level drift across CSV and JSON catalog exports.

Public repositoryMIT licensedPublished on npmLocal-only processing

Operating model

One studio. Three ways to build.

The form changes with the problem. The method does not: understand the workflow, choose the smallest useful system, and leave it easier to operate, safer to change, and easier to verify.

ProblemRepeatable problem
RXRworkflow first
Build modeFocused product

How the work is approached

Start with the workflow, not the technology.

The goal is not the biggest system. It is to make an important part of the operation easier to run, safer to change, and easier to verify.

The work starts with repeated manual tasks, unreliable handoffs, missing visibility, and outcomes that are difficult to verify.

Workflow mappingConstraint discoveryVerification targets

Founder-led, openly

A studio with a clear person behind the work.

RXR Code is an independent commerce software studio founded and operated by commerce engineer Gilriel Rodriguez. The studio builds focused products, publishes open-source tooling, and takes on selective client engineering around commerce workflows.

Project inquiry

Tell us what needs to work better.

Describe what is getting in the way—a storefront issue, an internal workflow, systems that need to exchange data, or repeated work that should be easier to operate. You do not need a technical specification.

View client engineering
contact@rxrcode.dev

Start a project

Tell us where the workflow breaks.

Choose the kind of problem, add enough context to understand the workflow, and tell us what should be better when it is finished. You do not need a technical specification.

What needs to work better?

Choose the closest fit. You can change this later.
Prefer email? contact@rxrcode.dev