LumiStack

For shops that sell in more than one place

Every place you sell. One shop.

Catalog, orders, CRM and website run as one workspace. An assistant sets it up from what you tell it you sell.

Tell us what you sellSee how it is built

  1. 1catalog behind every channel
  2. 3messengers in one inbox
  3. $0to start
  4. 1number on the bill

00

Tell it what you sell. It builds the stack.

  1. It switches modules and automations on for you.
  2. It asks for a credential with a form, and the form is the only thing that sees it.
  3. Every change it proposes is one you confirm.

01

One description, every storefront.

  1. Edit a product in Shopify and the catalog updates, then every other storefront.
  2. Each storefront carries the fields only it has: Etsy's materials, your site's slug, a second store's currency.
  3. Overriding a shared field on one storefront is next. A different title on Etsy, the same catalog everywhere else. The catalog already records which storefront wrote each value, which is the hard half.
  4. The catalog keeps the real stock number. The subtraction happens on the way out.

02

An order anywhere moves stock everywhere.

  1. An order on Etsy takes the unit from the catalog, and every other channel is told.
  2. A cancellation gives it back the same way.
  3. An oversell is recorded as −1 and published as 0, never hidden.

03

Every conversation in one list. Every person in one record.

  1. Telegram, Viber and the chat on your own site arrive in the same inbox today, whoever wrote and wherever they wrote from. Instagram and Messenger are next, then WhatsApp.
  2. You answer in the inbox and the answer goes back on the app that person used. A suggested reply waits for your Send.
  3. This is the CRM: behind every conversation sits the session that brought them, the lead with its status and owner, and the customer record it becomes, with their orders on it.

04

Point your agent at it. Undo anything it does.

  1. Claude Code, or any agent that speaks MCP, sees the catalog, the orders, the leads, the pages and the assets by name, and works the way you would.
  2. A change it proposes waits for your confirm. A page it writes waits for your publish. Rolling back is publishing the version before.
  3. Every change it makes is in the changelog with its undo, and the operations that cannot be undone are not in its toolset at all. You do those yourself.
A potter wrapping a finished mug in paper on a workbench, shelves of glazed pottery behind
One shelf, one description, and every place you sell reading from it.

Six things nobody else will say

Written down because they are true.

  1. Credentials are sealed and never shown back. There is no way to read them, including for us.
  2. Nothing is merged behind your back. Records group when you look, and you can overrule it.
  3. Order statuses never travel backwards.
  4. Editing never publishes.
  5. An oversell is recorded, not hidden.
  6. A suggested reply cannot send itself.

Pricing

You grow, then you pay.

One number decides the bill: orders or leads last month, whichever is bigger. Every tier has every module and every channel.

300 a month is Grow, $79
TierA monthOrders or leads a monthWhat differs
Start$0up to 50Every module, every channel. Set up with us.
Grow$79up to 500Unlimited connections per channel. Priority support.
Scale$199up to 2,000Custom automations built for you. A named person here.

Beyond 2,000 a month, talk to us.

Never counted twice. A person who writes to you and then buys is one order, not a lead and an order. An order counts once however many places it touched. We take the bigger of the two numbers, orders or leads, and bill on last month's count, so a slow month costs less.

Questions

Asked before anybody starts.

What is a conversation?
One person, on one app, writing to you. It opens in your inbox as a conversation and stays that one conversation however long it runs, so nobody arrives twice.
Beside it sits everything you know about them: the session that brought them, the lead with its status and its owner, and the customer record their orders hang on. Answering happens in the conversation, and the answer goes back on the app they used.
Which apps do conversations come from?
Telegram, Viber and the chat on your own site today. Instagram and Messenger are what merchants ask for most and are next, held up by Meta's review rather than by the work; WhatsApp follows them.
Each one is its own connector behind the same inbox, so a network being added changes nothing about the list you already read.
Do conversations decide my bill?
No. The bill follows orders or leads last month, whichever number is bigger, and a person who writes to you and then buys is counted once. Talk to as many people as you like on any tier.
What is the assistant, and what does it cost?
It comes with every workspace, including the free one, and there is nothing to switch on. Tell it what you sell and it works out the setup: which modules you need, a connection for each shop you run, which automations to switch on, and it says so in the conversation.
It proposes; you confirm. It has no key of its own and calls nothing on your data, so a change happens when you press the button and your own browser makes the request. That is a boundary in the code, not a promise in a prompt.
Why does the assistant not write my products or my pages?
Because that is a different job, and a bigger one. The assistant configures the platform. Your catalog, your orders, your leads and your website are work on your own data, and that is done by a coding agent you bring and point at your workspace.
The split is the point. Setup is a handful of switches somebody has to be sure about. Writing sixty product descriptions, rewriting a page, or answering "which leads asked about oak stools this week" is a session with a model that reads and writes for as long as the job takes, on your bill with your model, not ours.
How do I connect Claude Code?
Switch the MCP module on in Settings, and your workspace gets an address of its own. Give that address to Claude Code, Claude Desktop, Cursor or VS Code — one line for Claude Code, a line of configuration for the others — and your modules arrive as tools: products, orders, leads, conversations, pages, automations.
There is no key to paste. The client opens a browser, you sign in the way you always do, and the grant is one you can see and revoke. What the agent gets is what you can reach and nothing wider, and each tool is an operation the module already offers rather than a door cut for models.
What is an agent never handed?
Anything that cannot be undone. An operation the platform marks irreversible is not offered as a tool at all and is refused at the door if one is asked for, so deleting a site, forcing an order's status or sending a message to a customer stays a thing a person does.
Credentials are not on the list either. Your shop keys go into a sealed store through a form, and there is no tool that reads one back — not for your agent, not for ours.
Do I have to work through an agent?
No. Every module has its own screens, and they read first: you open a list, you look, and editing is a thing you ask for. An agent is faster on the bulk work and worse at nothing you would rather do by hand.
What happens to what I put in?
It stays yours and it stays separated. Every module holds your rows behind your workspace, and a read without it returns nothing rather than somebody else's row — that is enforced by the database, not by us remembering to filter.
Leaving deletes it. Every module has an endpoint that removes what it holds for you, and closing a workspace calls all of them, so what goes is everything rather than what somebody remembered.

Something here not answered? Ask us — a person writes back, usually the same day.

Start

Tell us what you sell.

We read it, build your workspace, and write back with your channels connected and your catalog in. Free under 50 orders or leads a month.

One email back from a person, usually the same day.