Claude Code + Trello boards · for ecommerce sellers

Claude Code that knows your shop, and a board that tells it what is due.

A ready workspace plus six Trello boards for the work that repeats. Runs as a chat panel in VS Code, no terminal.

Built by Stef from 6 years running ecommerce. Every rule in it was written after something went wrong.

EUR 129 at launch, one paymentNot on sale yet. Workspace alone EUR 89, one board alone EUR 37.

Sample session for an invented store, Kestrel Supply Co. This is what Monday looks like once your store and Trello are connected, which you do yourself in steps 6 and 11 of the guide. Card names are the real ones from the Operations board.

The problem

You have used Claude Code, or something like it. It read a CSV, wrote a script, caught something in your listings you had missed. Then the session ended and all of it went away.

So the next day you explained your margins again. And your supplier lead times. And which marketplace rejects images without a white background. By month three your notes file is 400 lines, half of it no longer true, and you cannot tell which half.

Missing context makes an agent useless. Wrong context makes it dangerous. A confident margin calculation built on a fact that stopped being true in April does not announce itself. It just approves a discount that loses money.

The other half of the problem is older than AI. None of the weekly operations work is urgent on any given day, so stock checks, supplier chases and margin reviews slip a week, then three. An assistant with nowhere to put that work, and no memory of your business, cannot fix either.

Stef, who built this setup

I built this structure for my own ecommerce businesses before it was a product, then rebuilt it from scratch as a clean template, so nothing from those businesses is in it. Every rule in it was written after something went wrong.Stef

Two parts, one setup

The boards hold what has to happen and when. The workspace holds what Claude needs to know to do it well. Your shop feeds both, one source at a time.

1

The boards

Six Trello boards for the work that repeats: stock, suppliers, listings, returns, support, growth tests. Every card has a description and a checklist, and the recurring ones have a day.

2

The workspace

A folder Claude Code reads every session: your business in CLAUDE.md, one rule per memory file, credential rules, and the convention for connecting your tools safely.

3

Your shop

Paste your store link and Claude drafts your setup from your own public pages. Then you connect your store, and a week later Trello, read only first.

What using it looks like

Three screens from an ordinary week at the same invented store. Claude does the reading and the writing; your part is a click, a sentence, or dragging a card.

1Your decision page

Claude asks on one page, not in chat

Anything that costs money or is hard to undo becomes a row with Claude's recommendation and the reason. Open the link on your phone whenever it suits you.

Your part: click Go or Skip

2Next session

It acts on your clicks before anything else

Every session starts by reading the page. Clicked rows get done, checked, and marked done on the page. Whatever still needs you is named in one line.

Your part: open Claude Code

3Customer Support board

See what you are working on apart from what you are waiting on

A ticket you replied to moves to Waiting with the blocker named on it, so Open only holds what nobody has touched. The fourth customer asking the same question becomes one Pattern card that gets the cause fixed.

Your part: drag the card
Invented store, Kestrel Supply Co. Rows and card titles are the samples that ship in the pack. The decision page needs a Claude plan with artifacts; without one, the same rows live in a plain file you edit, and Claude reads it the same way. Pausing listings needs your marketplace connected first, which you do yourself in the guide.

Why a notes file stops working, and what replaces it

Most people's fix for a forgetful AI is one long instructions file. It fails in three specific ways, and each has a specific fix in the workspace.

  1. It loads every session, so it is a cost you pay forever. The workspace has a hard size cap on the index and a one line check that enforces it at the moment you write, because a cap alone never holds.
  2. It cannot replace anything. When a fact changes you append the new version and both get read. Here it is one rule per file, overwritten in place, with file names that state the rule.
  3. It relies on you remembering the rules. Rules you have broken twice become checks that run before anything ships. That idea is what the whole package rests on.

What is written inside a card

You can build empty lists in ten minutes for free, and plenty of people sell exactly that. What you are paying for is what is inside the cards. Here is the middle of one card from the Operations board, in full:

StockMonin list 🔁 Weekly Routine

Stock check, top SKUs · 15 min max

Verdict first: you are looking for SKUs that will hit zero before a replacement can arrive. Nothing else in this card matters.

Reorder point = average units sold per day × supplier lead time in days × 1.5

The 1.5 is a buffer for a late shipment and a good week. Drop it to 1.2 only for a supplier you have never had a delay with. Raise it to 2 for anything coming from far away or through a single freight route.

What usually goes wrong: lead time is remembered, not measured. People use the quoted lead time. Use the last three actual ones. Sales per day is taken from a bad window: a SKU that sold 300 in a promo week is not selling 43 a day. And stock on hand includes units that are not sellable, because damaged, reserved and in transit units are not stock.

What to do with a hit: create a card in 📊 Stock Watch titled with the SKU. This card detects, it never orders. The ordering decision needs the supplier card, the minimum order quantity, the packaging you have on hand and the cash position, and that is a separate sitting. Keeping detection and execution in separate cards is deliberate. A detector that can also act will eventually act on a bad read.

Before you order: packaging. You cannot sell more units than you have packaging to put them in, and your packaging has its own lead time. Check it in the same sitting, or you will land 1500 units and be unable to ship them.

Weekly stock pass · 15 min12 steps
  • Confirm which account or brand is on screen before reading anything
  • Pull current sellable stock for your top 10 SKUs
  • A blank or zero export is a read failure, not a clean result. Re-pull before believing it
  • Compare each against its reorder point, not against zero

+ 8 more, in the order you do them

That is one card. The Operations board alone has 55.

  • 14 day refund, no explanation needed
  • Free Trello plan is enough
  • One payment, no subscription
  • Sample data invented and labelled

Set up from your own shop, not a blank file

Paste one prompt with your webshop or marketplace shop link and Claude drafts your setup from your own public pages: what you sell, your likely top ten, your brand basics and which tools your shop already runs, which becomes your list of what to connect. It marks every guess and asks only what no page shows, like your margin floor and what needs your approval. You correct a draft instead of typing into empty cards.

StockSample store: Fernlight, invented
Top 10 SKUs, reference
in list 🔁 Weekly Routine
  • 1Speckled mug, sageESTIMATE
  • 2Speckled mug, oatESTIMATE
  • 3Hanging planter, smallESTIMATE
  • 4Bud vase set of threeESTIMATE
  • 5Pour over setESTIMATE
  • 6Hanging planter, largeESTIMATE
+ 4 more · ranks are estimates until your orders are in
Drafted by the 15 minute pre-fill. You correct it, then it is yours.
One card after the prompt. Sample business, invented. See the full pre-fill sample

What is included

The Claude Code workspace

  • A template workspace: CLAUDE.md written to be edited, a memory index, 17 worked example memory files and the credential rules
  • A 12 step setup guide, zero to working. Every step has a check and the symptom you see when it went wrong
  • The conventions, about 4,000 words, written from things that went wrong rather than from an outline
  • The pre-fill prompt shown above
  • A decision page: one page with Go and Skip buttons where Claude puts every decision it needs from you
  • Three checks that run by themselves: one reads each reply before you see it, one stops the memory index growing past its cap, and a daily sweep lists every overdue or undated Trello card
  • 12 months of updates

Six Trello boards

  • Operations55 cards
  • Customer Support18 cards
  • Growth and Testing26 cards
  • Content and Partnerships19 cards
  • Decision Record14 cards
  • People and Handover19 cards

The boards hand work to each other: a support ticket pattern becomes a fix on Operations, a test result becomes a change.

What you need, and what you do yourself

VS Code (free), the Claude Code extension and a Claude plan that includes Claude Code, a free Trello account, and one API key from your store. No terminal: Claude Code runs as a chat panel next to your files and you talk to it in plain language. You do the clicks yourself, with the guide showing every one. Nothing connects to your store until you connect it, and keys go in a folder Claude is blocked from reading.

Who it is for

You sell physical products, somewhere between 5 and 200 SKUs, alone or with one part time helper. You have tried an AI assistant and noticed it has no memory of your business, and the weekly checks you know matter keep slipping.

Who this is not for

I would rather lose the sale than take it from the wrong person.

  • You are not selling yet. The memory holds your suppliers and margins. With none, there is nothing to put in it
  • You want it running while you sleep. This is a structure for working with Claude, not an unattended system
  • You want it installed for you. You do the setup, with a written guide. No calls or screen shares
  • You want ecommerce strategy. It will not tell you what to sell. The numbers in the examples are invented
  • You will not open it twice a week. Then it does nothing for you, and no setup would

Price

One payment, no subscription. Launch prices, not on sale yet: join the list below to hear the day it opens.

Recommended

Workspace + 6 boards

EUR 129

Everything on this page. EUR 39 less than buying the two parts separately.

Workspace only

The workspace

EUR 89

The workspace, guide and conventions, without the boards. For people who already run their own task board.

No setup

Operations board

EUR 37

One Trello board, no Claude needed. Copy it, 45 minutes of filling in, done the same day.

“This package has helped me a lot improving my current E-commerce Business with a nicely setup claude code workfolder with easy steps to implement”

Stanley, ecommerce seller · got the package free to test

One prevented mistake pays for it: a stockout in your best week, a discount approved on a margin that forgot the marketplace fee, an API key pasted into a support thread. Join the list for launch day.

FAQ

Do I need to be technical?

No. There is no terminal in this setup. Claude Code runs as a chat panel inside VS Code, a free editor, with your files listed next to it, and you talk to it in plain language. The one technical step is pasting an API key from your store or task board, and the guide shows where each one lives. If you can install an app and copy a key, you clear the bar.

Does it work with my store platform?

The conventions do. Ready made integrations are not included for any platform, on purpose: every store has a different API and a different set of traps. What ships is the pattern and the security rules, and the guide walks you and Claude through building your first connection against your own store.

What support is included?

The files, 12 months of updates, corrections to anything wrong in the package, and one email reply to a question about what something in the documentation means. Not included: help installing it on your machine, debugging your platform's API, calls or screen shares. That is stated here rather than after you buy, because scope explained afterwards reads as a refusal.

Is this a course?

No. No modules, no community, no calls. It is a template workspace, written guides and the boards. If a written guide is not how you learn, this is not the format for you.

Do I need a paid Trello plan?

No. The free plan is enough, and the boards are built to stay inside it. No Power Ups required.

Do the recurring cards arrive already repeating?

No, and neither does anyone else's. Trello's repeat setting exists only in its own interface, not in its API, so no Trello template can ship with it switched on. The setup guides walk you through switching it on for each recurring card.

Is any of this from your actual business?

The thinking is. The data is not. Every store, supplier, SKU and number in the package and on this page is invented, and the package says so in writing. Kestrel Supply Co. does not exist.

What if it does not work for me?

Email within 14 days and you get a refund, no explanation needed. Please read the not for list above first, so neither of us spends that time.

Will it be out of date in six months?

The conventions will not. They are about how memory and checks work, not about any product's buttons. The setup steps could age if Claude Code changes, which is what the 12 months of updates covers.

Teach it once.

Your shop, your rules and your weekly checks, written down where Claude reads them every session, with dates on the work that keeps slipping.

EUR 129 at launch, workspace plus 6 boards. One payment.

No payment now. You join the MOGA World email list and hear the day it opens, before anyone else. Unsubscribe in one click.