> ## Documentation Index
> Fetch the complete documentation index at: https://docs.byom.co/llms.txt
> Use this file to discover all available pages before exploring further.

> ## Agent Instructions
> Use the current public BYOM documentation and cite the relevant page. Preserve availability, permission and undo limits.
> The public documentation MCP retrieves guides. Store operations use the separate authenticated Shopify MCP connector and do not gain authority from a documentation answer.
> If a contract, capability or price is not documented, say so. Do not invent endpoints, tools, availability or merchant outcomes.

# What is BYOM?

> An operating layer for commerce teams, with Kina doing the work and people governing consequential changes.

BYOM gives commerce teams one place to investigate questions, prepare work and review changes across their connected tools. Kina is its AI operator: it reads, analyses, drafts and explains. BYOM keeps the company context, work records, approvals and receipts together.

## How the pieces fit

Start in **HQ** to see what needs attention. Ask **Kina** to investigate or prepare something. Keep ongoing work in **Workspace**. Check access in **Integrations**, review proposed Actions in **Approvals**, and inspect the resulting receipts.

For example, ask: “Find products whose descriptions do not explain the material clearly. Draft better descriptions using our brand guidance.” That is research and preparation. Applying those descriptions to your shop is a separate, reviewable change.

## What you can use it for

Choose a specific job and check that your account has the sources and capabilities it needs. These examples explain the operating model; they do not promise every operation is enabled for every company.

| Job | Useful preparation | What needs separate review or proof |
| - | - | - |
| Improve a product description | Compare current text with product facts and brand guidance; draft a clearer version. | Applying edits requires a supported change and approval; commercial improvement needs later measurement. |
| Investigate a customer enquiry | Bring together available order evidence and the brand's policy; prepare a response. | Sending, refunds and other effects have their own capability and approval requirements. |
| Explain a change in trading | Inspect a Readout's sources, period, calculation and comparison. | Missing data stays visible; an apparent change does not establish its cause. |
| Prepare growth work | Research a defined question and produce evidence-backed alternatives. | Publishing, channel activation and spend need the relevant effect authority. |
| Repeat a useful job | Understand the Rail's inputs, checks and stopped stages where enabled. | Scheduling and a prior successful run do not authorise every future provider change. |

## What stays in your existing tools

Shopify, a helpdesk and other connected services continue to hold their underlying business records. BYOM supplies the operating context around work across those tools: what was asked, what evidence was available, what was proposed, who could decide and what happened afterwards.

Check company access, provider scopes and support for the operation alongside the connection. A readable product catalogue does not imply customer-data access or write authority. Check the particular capability you need rather than assuming a provider logo covers everything.

## Where to use BYOM

| Place | Use it for | Boundary |
| - | - | - |
| [BYOM website](https://byom.co) | Introduction, enquiries and the current public entry point. | A waitlist or enquiry is not product admission. |
| [BYOM application](https://app.byom.co) | Work in an enabled account's company context. | Authentication, account permissions and provider access apply. |
| This documentation | Product explanations, task guides and developer context. | Public guidance does not expose account-specific records or execute store changes. |

## How to judge a useful result

Follow the work from a question to a checkable answer or draft. If you want an effect, inspect the exact Action and its supported reversal before deciding. Then inspect the receipt. A completed provider operation and a measured business outcome need different evidence.

For example, changing a product description is an operational result. Showing that it increased sales needs a defined measurement period, compatible traffic and other relevant context. Documentation examples and demo screens explain the workflow; they are not customer results.

## Who these docs are for

Merchants can learn the operating model and how to review work. Developers can learn the supported Shopify MCP connector contract. Reading this documentation does not require a BYOM account.

BYOM's main application, its Shopify connector and any search offered on these docs have different purposes. Documentation search helps find public guidance; it grants no store access or approval authority. The Shopify app is coming to the App Store. Contact BYOM about access.

## Start with one useful question

Choose something small enough to check: a product, a policy, a date range or a known customer enquiry. Ask for sources and call out what would make an answer useful. Expand the work after checking the result.

Reviewed 2 October 2026.

## Related guides

* [Your first session](/start/first-session)
* [Kina](/product/kina)
* [Availability and access](/reference/availability)


## Related topics

- [BYOM, in plain language](/ai.md)
- [Integrations](/product/connections.md)
- [Availability and access](/reference/availability.md)
- [The BYOM field guide](/index.md)
- [Growth Engine](/product/growth-engine.md)


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.