Skip to content
heapbyte - A name of excellence

Service · Optimise & Scale

AI Commerce & Automation

Narrow, evaluated AI applied to merchandising, catalogue enrichment and support workflows. No autonomous agents writing to your live store.

  • OpenAI / Anthropic APIs
  • Embeddings & vector search
  • Node.js
  • Shopify Flow
Group
Optimise & Scale
Starts with
Technical audit
Delivery
Git + staging theme
Handover
Written documentation

01Overview

Most AI proposals for Shopify merchants start from the technology and work backwards to a use case. We start from the operational cost. If a task is high volume, repetitive, and currently done by a person copying between systems, it is a candidate. If it needs judgement, brand voice nobody has written down, or carries legal risk, it stays with a human.

Everything we ship is evaluated before it reaches customers. That means a labelled test set, an agreed accuracy threshold, and a measurement you can repeat after a model or prompt change. Without that, quality drifts silently and nobody notices until a customer does.

Nothing writes to the storefront unattended. Generated catalogue copy, attributes and recommendations land in a review queue with a clear diff and a one-click revert, so your merchandising team stays accountable for what customers actually see.

02The problem

AI in commerce is mostly demos. The value sits in unglamorous places: catalogue data quality, internal search relevance, support deflection and operational triage — work that is repetitive, measurable, and expensive when done by hand.

03You will recognise this if

  • Catalogue copy and attributes are entered by hand
  • Support answers the same questions repeatedly
  • Merchandising decisions rely on manual review
  • Product data quality varies by whoever entered it
  • An AI pilot produced impressive demos and no measurable saving

04How we work on it

  1. 01

    Pick boring problems

    We target repetitive, high-volume work with a measurable cost, not headline use cases. The first question is always what this currently costs in hours.

  2. 02

    Evaluate before shipping

    A labelled evaluation set and an accuracy threshold are agreed before anything reaches customers. If the threshold is not met, the feature does not ship.

  3. 03

    Human in the loop

    Generated output is reviewable, diffable and reversible. Publishing to the storefront is an explicit action by a person, never a side effect.

  4. 04

    Grounded, not guessed

    Answers and enrichment are grounded in your own catalogue, policies and help content through retrieval, which is what keeps output factual rather than plausible.

  5. 05

    Cost control

    Token and latency budgets, caching and cheaper-model fallbacks so the feature stays economical at catalogue scale, not just in a pilot.

  6. 06

    Monitoring and rollback

    Quality, spend and failure rates are tracked after launch, with a documented path to turn any of it off without touching the theme.

04What you get

Deliverables, not decks.

  • Use-case assessment with an hours-and-cost model
  • Labelled evaluation set and agreed accuracy thresholds
  • Retrieval layer grounded in your catalogue and policies
  • Production pipeline with a human review UI
  • Shopify Flow and Admin API automations
  • Quality and spend monitoring dashboard
  • Prompt and model change process
  • Documented rollback path
ai/enrich-catalogue.ts
1// field-data first — never lab scores alone2const budget = { lcp: 1800, tbt: 120, cls: 0.05 };3 4onCLS(send); onINP(send); onLCP(send);5// regressions fail the deploy, not the quarter

Delivery pipeline

  1. Audit
  2. Scope
  3. Build
  4. QA
  5. Measure

05What changes

Hours returned
Repetitive catalogue and support work moves to a reviewed pipeline, so your team spends its time on decisions rather than data entry.
Measurable quality
Accuracy is a number against a fixed evaluation set, not an impression, which makes model and prompt changes safe to make.
Controlled spend
Token, latency and failure budgets are monitored from day one, so cost scales with the catalogue predictably.

06How an engagement runs

  1. 01

    Audit

    We map the operational workflows that are actually expensive and score them for volume, risk and measurability. You get a shortlist with a cost model attached.

  2. 02

    Scope

    One use case is chosen, with an evaluation set, accuracy threshold and cost ceiling agreed in writing before build starts.

  3. 03

    Delivery

    Built with a review interface from the first iteration, evaluated against the test set, then monitored for quality and spend after launch.

07Stack

  • OpenAI / Anthropic APIs
  • Embeddings & vector search
  • Node.js
  • Shopify Flow
  • Admin API

09Questions

AI Commerce & Automation

Send us the store and the symptom.

A senior engineer reads it, tells you what is actually going on, and scopes only what the evidence supports.