Behind a local Judaica shop is a working system for turning everyday requests into catalog updates, custom software, reviewed imagery and ongoing care.
Actual storefront screens · September 8, 2026 · Views adapt to your screen. Current products and availability may change.
The starting point
A shop needs more than a shopfront.
Vancouver Judaica makes Jewish ritual goods more accessible on Canada’s west coast. Its stakeholders know their community. Running a digital catalog, preparing product photography, configuring Shopify and maintaining custom software are different jobs.
The project began as an agency inside a repository: brand guidance, design components, product research, commerce tooling and an operating playbook. The website grew out of that system. The same system continues to handle the work that arrives after launch.
The operator harness
A request becomes work. The work comes back with evidence.
An operator harness is the instructions, tools, project memory and checks that let people and AI agents run a business process together. Kobi directs the work through Codex and Claude Code; specialist roles carry out bounded tasks.
01 / ReceiveUse the conversation already happening.
An email, an invoice, a photograph or a WhatsApp voice note carries the request.
02 / UnderstandReconcile it with the business.
Identify the product, the stakeholder, what is known, what is missing and which decision is needed.
03 / ExecuteBring the right tools to the job.
Research, image generation, Shopify APIs, code changes and deployment procedures share one working context.
04 / VerifyCheck the actual result.
Review the content, read back saved changes, test the live experience and report to the relevant conversation.
Three examples from the project
Ordinary inputs. A substantial operation behind them.
01
From supplier email to sellable catalog.
Supplier paperwork and informal product photos became structured product records. The harness reconciled existing products with vendor-specific items, researched product facts and proposed pricing, prepared images, and organized customer-facing collections.
One photo intake preserved 22 source-image occurrences and grouped them into seven product families. Uncertain details stayed visible in a non-purchasable preview while the operator consolidated the questions for stakeholders. In a separate supplier intake, received products progressed through Shopify and into the production-backed storefront.
The reusable capability: a stock-intake process with provenance, product matching, pricing research, media review and inventory reconciliation.
02
From a voice note to a coordinated response.
A stakeholder sent Hebrew voice feedback over WhatsApp about promotion and launch readiness. The workflow retrieved and transcribed the audio, interpreted the request, prepared campaign directions and carried the review forward through email.
The business did not need to learn a project-management interface to contribute. The operator connected the communication to the relevant work and approvals. When a campaign update landed in the stock conversation, the process corrected the topic and moved follow-up monitoring to the campaign thread.
The reusable capability: meet stakeholders in their existing channels, then maintain a coherent record of requests, decisions and delivery.
03
From visual feedback to a tested release.
Product and collection imagery moved through source preservation, image generation, identity checks and visual review. Generated concepts were tracked separately from approved customer-facing assets. Presentation could change while the actual product remained the reference.
The same operating loop handled software defects. An oversized collection hero was traced to a missing responsive image wrapper, corrected, and checked on desktop and mobile alongside an unaffected collection. Later production checks covered navigation, guided purchasing, product inquiries and checkout handoff.
The reusable capability: feedback can trigger design work, data work or engineering, with verification appropriate to the change.
Under the hood
Custom where the business needs it.
The public storefront is a custom React storefront using Shopify Hydrogen and Shopify’s Storefront API, deployed on Cloudflare Workers. Shopify supplies the commerce backend and checkout. Cloudflare serves the custom experience. It is a headless sales experience rather than a standard Shopify Online Store theme.
The customer experience
Custom layouts, guided purchasing, preference-aware presentation, local context and responsive product discovery.
React · Hydrogen · Storefront API
The commerce foundation
Products, variants, stock and checkout backed by Shopify, supported by CLI and API tooling for controlled changes.
Shopify · catalog tooling · readback
The operating layer
Stakeholder intake, research, brand rules, image workflows, specialist roles, shared records and release checks.
Codex · Claude Code · human operator
The ongoing care
Cloudflare deployment procedures and scheduled checks for the public storefront, responsive behavior and protected commerce journeys.
Cloudflare Workers · automated QA
What changes for a small business
Software that takes on the work.
A conventional software subscription gives a business another interface to operate. Here, the delivery includes the process around the application: interpreting requests, preparing changes, coordinating decisions and checking the outcome.
Stakeholders can contribute through email and WhatsApp, including attachments and voice. Other channels can be connected through their available APIs or tools. A business may standardize its communication for clarity; the harness does not require everyone to adopt a new front door.
The operator retains judgment over commitments, product truth and publication. Agents do the research and execution. Reusable skills and durable records make that work repeatable across sessions.
After launch
Maintenance is part of the operation.
The project has an active hourly storefront-health schedule and separate commerce checks every six hours when permitted by its observance policy. Checks cover critical pages, catalog visibility, guided help, support, responsive layouts and runtime errors. Commerce tests stop short of payment and order completion.
That changes who handles maintenance. The business can report a problem through the existing conversation; the harness supplies the investigation and repair workflow. Dependencies, integrations and infrastructure still need care, and the operating process includes that responsibility.
At launch, the application checks passed while alternate-domain redirects remained an explicit follow-up. The monitoring system retained those failures rather than relabeling the whole operation as healthy.
The economic shift
A broader scope becomes practical.
Custom commerce, catalog operations, visual production, stakeholder coordination and ongoing QA would usually span several specialist services. AI-assisted execution lets one operator coordinate that range of work and turn repeated procedures into reusable software and skills.
The project demonstrates that breadth. It does not yet establish a measured cost saving, conversion uplift or long-term reliability rate. Performance and cost efficiency are architectural goals; business outcomes will need post-launch data.
Bring your business, not a software specification.
What work is falling between your tools?
Tell us what arrives, who needs an answer and what has to happen next. We’ll explore the operating process with you.
