Shopify Overview

Documentation Index

Fetch the complete documentation index at: https://docs.hiveku.com/llms.txt

Use this file to discover all available pages before exploring further.

Hiveku’s Shopify integration lets you build a headless Next.js storefront on top of any Shopify store. Products, inventory, payments, taxes, fulfillment, and shipping all stay in Shopify (the back-office your team already knows). Hiveku owns the storefront UI: pages, components, SEO, conversion features, customer accounts, subscriptions self-service, and reviews. The result: an AI-search-friendly, agency-grade storefront that ships in one prompt, with no Shopify theme limitations and no custom code maintenance burden.

​

Who it’s for

• DTC brands that want a custom storefront without paying $5–15k for a Hydrogen agency
• Agencies managing multiple Shopify shops who need server-rendered SEO and per-shop tuning
• Existing Next.js projects that want to add Shopify commerce without rewriting

​

Why headless on Hiveku, not a Shopify theme

Standard Shopify themes (Liquid) and even Online Store 2.0 ship rendered HTML. They work, but you trade flexibility:

​

What you get when you connect Shopify

A single OAuth connection unlocks the whole stack. The AI agent then scaffolds whichever pieces you need:

​

The architectural split (important to understand)

Hiveku’s Shopify integration is opinionated about a clean separation:

• Shopify owns: products, inventory, orders, payments, taxes, shipping, fulfillment, subscription billing, customer payment methods (PCI), webhooks for state changes.
• Hiveku owns: the storefront pages, cart UI, customer-account UI, reviews data, conversion components, JSON-LD SEO, automation (workflows triggered by Shopify events), CRM contacts (linked from orders), the AI-agent surface.

We deliberately do not mirror Shopify state into Hiveku’s database (no order copies, no contract copies). Shopify is the source of truth and we render fresh from its APIs each request. This avoids the classic sync-nightmare problem and means your Shopify admin always shows what’s actually true. The exceptions to “no mirroring”:

• CRM contacts (orders auto-upsert a contact row keyed by email — gives you LTV rollups in crm_contacts.shopify_total_spent_cents)
• Reviews (Hiveku stores them so we can serve them headless-friendly; Yotpo/Loox can’t because they’re Liquid-only)
• Per-connection settings (CRO toggles, subscription copy overrides — small config rows, not transactional state)

​

Multi-shop and multi-account

Hiveku is built for agencies and operators who manage more than one shop:

• Connect one Shopify store as the account default — every project under that account inherits it.
• Override the connection at the project level when an agency manages multiple brands in one workspace.
• Per-shop settings for CRO, subscriptions, customer-account auth — the fashion brand and the electronics brand don’t share thresholds.

​

Hard preconditions to know

• Shopify Payments is required for native subscriptions (gates ~12 countries: US, CA, UK, AU, IE, NL, NZ, ES, IT, DE, FR + a few more). Outside those, subscriptions need a third-party app (ReCharge integration is a roadmap item).
• Shopify Subscriptions (the free first-party app) must be installed before subscriptions render. Hiveku detects + warns if it’s missing.
• Customer Account API application must be registered in Shopify admin before the customer-account scaffold’s OAuth callback works.
• Headless-incompatible apps (Yotpo, ReCharge, Bold, ReConvert, Liquid-only search apps) will not work on the Hiveku storefront. Hiveku ships first-party replacements for the most common ones — see App Compatibility below.

​

Where it lives in the dashboard

​

Next steps