1-833-643-7737 Talk to us
Services

The scope, written out.

Five engagements clients buy, and one more that is only starting to be bought. Each is listed as what actually gets built, so you can price it, staff it, or hand it to someone.

Shopify Plus builds

Shopify Plus

A storefront built to the shape of the catalog rather than fitted around a purchased theme. Liquid where the platform should carry the rendering, Hydrogen and Oxygen where the front end needs to be its own application.

  • Custom Liquid theme development, built from nothing purchased
  • Metaobjects driving content and merchandising
  • Hydrogen storefronts in React and Remix, deployed on Oxygen
  • Storefront API data loading, caching and route-level control
  • Deep variant matrices and configurator models
  • Subscriptions and bundling built into the theme core
  • Multi-region and multi-currency on Shopify Markets
  • Page speed held as a requirement, not measured at the end
Sections assembling from metaobjects

Migrations and replatforming

Moving a live business onto Shopify from WordPress, Magento or BigCommerce, with the catalog restructured to what it actually needs on the way across.

  • Catalog, customers and order history moved with relationships intact
  • URL and redirect maps so rankings survive the cutover
  • Data model rebuilt around the real product architecture
  • Parallel running and reconciliation before the switch
  • Zero-downtime cutover with a rollback path
  • SEO designed into the build rather than added afterward
Records leaving one shape, landing in another

Custom development

The parts of a commerce business that no app covers, built as software and documented so your own team can own it.

  • Wholesale and B2B portals
  • Subscription, bundle and recurring logic
  • Checkout extensions and Shopify Functions
  • Internal tools and admin surfaces
  • Pricing data audits, flattening the grid in R to surface outliers and gaps
  • Price surface modeling, so a new size or quantity prices consistently with the grid around it
  • Private apps on Admin GraphQL and webhooks
  • Serverless services on AWS Lambda and Cloudflare Workers
One call path through the modules

Integrations

Getting Shopify and the systems around it to agree on the same numbers, continuously, including when one of them is down.

  • ERP, OMS and PIM sync over Admin GraphQL and webhooks
  • Third-party warehouse and 3PL inventory
  • Multi-location inventory and available-to-promise
  • Order routing and allocation across locations
  • Tax, duties and cross-border requirements in platform
  • Payment rails presented per market
Four systems, one set of numbers

CRM

The email, SMS and push program treated as software rather than as a campaign calendar. Built alongside the storefront where there is one, so the store and the program hold the same view of a customer instead of half each.

  • Architecture audits over the flows, automations and segments already running
  • Migrations between platforms, or a first program built from nothing
  • Custom journeys, triggers, templates and hosted pages
  • Data integrations to Shopify, warehouses, ERPs and internal APIs
  • Omnichannel orchestration across email, SMS and push
  • Deliverability: sender reputation, authentication and list hygiene
  • Consent and suppression carried in the data model, not in a spreadsheet
  • Reporting that ties sends to orders rather than to opens

Run on Salesforce Marketing Cloud and Marketing Cloud Next, Data Cloud, Klaviyo, Braze, Iterable and Customer.io.

One field, three journeys
AI and agentic commerce

Catalogs are being read by software that never loads the page.

Assistants search catalogs, build carts and check policies through published servers. The work is making a store answer correctly on that surface, and deciding what it should refuse to answer.

The same store, as an assistant receives it

AI visibility

An llms.txt, structured data, product feeds and catalog semantics, so an assistant reads the range correctly and cites it as it is rather than as it guesses.

Storefront MCP and UCP

Shopify's catalog, cart, policy and order servers connected and tested against real questions, so an agent can search, add to a cart, quote a policy and check an order.

Custom MCP servers

Your own systems on the same standard: inventory, order status, pricing rules and anything else an agent should be able to ask about directly.

/api/ucp/mcpsearch_catalog · lookup_catalog · get_product
/api/mcpget_cart · update_cart · search_shop_policies_and_faqs
/llms.txtwhat the range is, in the form a model reads first

Shopify’s own servers, on any store that publishes them. Reaching them is configuration; answering well on them is the engagement.

Platforms we excel in

Where the work actually runs.

  • ShopifyPlus, Markets, Functions, Oxygen
  • SalesforceMarketing Cloud/Next, Data Cloud and Data 360
  • CloudflareWorkers, KV, D1, Pages and the edge
  • AWSLambda and the services around it
  • Google CloudRun, functions and BigQuery
  • Microsoft AzureFunctions and hosted services

We work in whatever stack is already in place. These are the ones we have shipped most on.

Also offered

Scoped into a build, or taken on their own.

  • UI/UX and conversionInterface work and CRO, argued from behavior data rather than from opinion.
  • PageSpeed and performanceLCP, INP and CLS taken as targets, measured on real devices and tuned into the green.
  • AccessibilityWCAG conformance, keyboard paths and screen reader passes over the live theme.
  • Search Engine OptimizationTechnical SEO, structured data and catalog semantics, designed into the build.
  • Analytics and measurementServer-side GA4, event design and attribution that survives a cookie prompt.
  • Behavior analyticsSession replay and heatmapping, feeding the design decisions that follow.
  • App and plugin auditsWhat each installed app is costing in speed, subscription and risk.
  • Reporting and BIDashboards built on real order, catalog and inventory data.
  • QACross-browser and cross-device passes, with checkout regression on the live theme.
  • Support and maintenanceRetainers for platform work, monitoring and the queue after launch.

Tell us what you are working on.

A scope, a brief, or a store that already exists.