Products from Shopify.
Stories from you.
Capa syncs your Shopify catalog in as entries, so lookbooks, guides and landing pages point at real products. Reviews and in-store items can come along too, and every page reads from the edge cache.

Ridge Shell Jacket
$189
SMLXL
Made for the wet side of the mountain. Our guide Kai wore it up the Cascades for a week and came back dry.
4.8 from 126 reviews
- Shopify product, synced in
- Story written in Capa
- Reviews from Judge.me
Your store,
synced in as entries.
Connect Shopify yourself from Integrations. Products and variants, collections, pages, blogs, menus and metaobjects arrive as content you can filter, reference and read through the same API as everything else. Judge.me reviews and Square catalogs are set up on request.
- ShopifyConnect it yourself
- Products and variants
- Collections
- Pages
- Blogs and articles
- Menus
- Metaobjects
- Judge.meOn request
- Reviews
- SquareOn request
- Items and variations
- Categories
- Inventory
- Locations
- Images
Stories that point
at real products.
Add a Model field to a lookbook or a buying guide and pick products from the synced catalog. The page reads the story and its products in one request, with relations expanded up to four hops deep.
# The lookbook and its six products, in one read
$ curl -G https://cdn.capacms.com/api/entries/lookbooks \
--data-urlencode 'select=title,intro,products(title,handle,limit:6)' \
-d limit=1 \
-H "x-api-key: $CAPA_KEY" \
-H 'Capa-Version: 2026-10-01'Set the drop
for nine sharp.
Schedule the campaign page, the banner and the collection story for one moment in your store’s timezone. Capa shows the same moment in UTC, so nobody does the maths at 8:58.
- Unpublish on a schedule too, so the sale ends on time.
- Everything going out next, grouped by when, with Publish now, Reschedule and Cancel.


Fast on your
busiest day.
Published content is served from the nearest of Fastly's edge locations, typically in 20 to 50 ms. A publish clears only the entries and models it touched, and the page is live in under three seconds. If the origin has a bad minute, the edge keeps serving the last good copy.
- On Pro and up, Capa puts content back in cache before shoppers ask for it.
A request log: reads answered from the edge cache, typically in 20 to 50 ms, and a publish that purges only the keys it changed.
One upload,
every size the theme needs.
Ask the image URL for a width, a crop and WebP or AVIF, and it comes back cached at the edge for a year. Replace the photo and every size refreshes.

- Source JPEG
no transform7,243 B - JPEG
?width=4004,222 B - AVIF
?width=400&format=avif1,740 B - WebP
?width=400&format=webp1,380 B
One 600 × 400 JPEG asked for at 400 px wide, measured on Capa’s image pipeline in September 2026.
Sell the story,
not just the SKU.
Connect your store and see your catalog in Capa today.
More ways teams use Capa
- DevelopersAPIs, agents and an SDK you will like→
- Marketing teamsShip pages without waiting on a deploy→
- AgenciesOne login for every client you run→
- Content editorsEdit what you see, publish when it is right→
- Multi-site & brandsMany sites, one source of truth→
- Apps & every screenWeb, mobile and anything that reads an API→