BRT embed platform

Keep your site. Add your store.

Your Battle Ready Tech catalog, class and range schedules, and a working cart, on the website you already run. Any platform you can add HTML to.

<script src="https://shop.yourstore.com/embed/v1/brt.js"
        async></script>

<div data-brt="product-list"
     data-slug="new-arrivals"></div>

The path to a page

One tag. One element. Real products.

1

Connect a store host

Battle Ready Tech sets up a subdomain of your own domain, and you add one DNS record for it. Nothing else works until that address is live.

2

You add the runtime

One script tag, anywhere on the page. It adds a single name to the page and loads nothing on pages that use no components.

3

You place components

Empty elements with a data-brt type and a slug. Products, collections, search, class schedules, range availability, and a cart that survives the trip between the two origins.

Any platform

No framework, no build step, no lock-in.

Shopify, Wix, Squarespace, Magento, Webflow, a Rails or Laravel app, a static site, hand-written HTML. If you can paste a script tag and a div, you can embed.

WordPress has a plugin that renders server-side instead, so the products are in the page source before any script runs.

When BRT is slow

Your page still loads.

Every call has a short timeout, then a cached copy, then an older cached copy, then a sized empty space. A component that cannot answer leaves a gap. It never leaves an error on a shopper's screen.

Partial failure is normal and contained: one dead slug never blanks a page.