For Shopify teams that ship every week
Agents build the experiences.
Your team decides what ships.
Pack gives your team and your AI agents one place to build, test, and release every version of your storefront. Server-side, through a native MCP server, with your review before anything goes live.
- Build
- Visual Customizer
- Test
- Server-side A/B
- Release
- Content releases
- Agents
- Native MCP
Products /Daily Barrier Lotion
Release: Fall dropFree shipping on orders over $50
Shop / Body /Daily Barrier Lotion
Bestseller1 / 4Daily Barrier Lotion · 200 ml
Daily Barrier Lotion
★★★★★4.8 · 2,341 reviews
Size: 200 ml
01 — The shift
Code, content, tests, and landing pages all ship separately.
Four streams, four queues. QA and engineering spend the week untangling them. Here’s the same Fall drop, shipped two ways.
9 days
- 4 queues
- 4 handoffs
- 0 tests run
- ContentShipped day 9
- CodeStuck behind two bugs
- A/B testsSlipped to next sprint
- Landing pagesSlipped to next sprint
- 1Day 1
Maya · Merch
Hero copy goes to the CMS, the CTA test to the testing tool, the landing page to a page builder.
- 2Day 3
Engineering
The test needs a code change. It waits behind two bugs.
- 3Day 6
QA
Three previews, three environments. The copy no longer matches the test variant.
- 4Day 9
Engineering
Hero ships. The test and landing page slip to next sprint.
01
Ship without waiting
Your team edits in Pack. Agents draft into a release. Ship when you're ready — no dev ticket required.
02
A controlled surface for AI
Agents work through Pack's MCP server, straight into a content release your team reviews before it goes live.
03
One workflow, one release
Publish, test, and personalize in the same content release. Review once. Ship together.
02 — Behind the scenes
Agents draft. Your team reviews.
You ship when it's ready.
Here’s what the agents actually did on Fall drop. Every call went through Pack’s MCP server and landed in the release for review — nothing went live on its own.
01 / Publish
The new hero, drafted from real reviews.
Agents read your storefront and call the same tools your team clicks. Both land in the same release.
agent — ~/halden-storefront — publish
~/halden-storefront main ❯ agent --mcp pack
⏺pack - get_page (MCP)(slug: "barrier-lotion")
⎿Hero banner · “Daily Barrier Lotion”
⏺pack - search_reviews (MCP)(product: "barrier-lotion", top: 3)
⎿“still hydrated hours later” ×412 · “texture” ×103
⏺pack - update_section (MCP)(section: "hero", heading: "Moisture that lasts until tomorrow.")
⏺pack - add_to_release (MCP)(release: "fall-drop")
⏺Added to Fall drop. Maya has 1 change to review.
>
02 / Test
A server-side test on the CTA, no flicker.
Configure, expose, and read results — from the editor or an agent. Tests ship inside the release they belong to.
agent — ~/halden-storefront — test
~/halden-storefront main ❯ agent --mcp pack
⏺pack - create_experiment (MCP)(page: "barrier-lotion", element: "hero.cta")
⎿exp_cta_price · 50/50 split
⏺pack - set_variant (MCP)(id: "exp_cta_price", variant: "B", text: "Add to bag — $38")
⎿Variant B saved
⏺pack - add_to_release (MCP)(release: "fall-drop")
⏺Test attached to Fall drop. It goes live when you approve.
>
03 / Personalize
Returning customers get a different hero.
Build as many experiences as you need and serve each one server-side. Use Pack’s audiences, or connect your own logic to decide who sees what.
agent — ~/halden-storefront — personalize
~/halden-storefront main ❯ agent --mcp pack
⏺pack - create_audience (MCP)(name: "returning", signal: "orders >= 1")
⎿18,204 shoppers matched
⏺pack - create_experience (MCP)(audience: "returning", page: "barrier-lotion")
⏺pack - set_section (MCP)(section: "hero", variant: "refill-bundle")
⏺Drafted in Fall drop. Waiting on your review.
>
04 / Blueprint
Built on Blueprint.
Our opinionated Hydrogen theme — production-tested and open source. What your team and your agents build on.
View repo<1s
LCP out of the box
2–3×
Faster than themes
OSS
Fork it, own it
A/B
Server-side tests wired in
MCP
Hooks on every surface