Implementation Pricing Docs
AI harnessPart of AI in Fulfil, the ERP for Shopify brands

Fulfil is the harness for your AI agents.

A model can reason. To do work in your business it needs records to read, actions it may take, limits, an approval step and a log. That is the harness. Fulfil has it for your orders, your inventory, your fulfillment and your accounting, so what your team builds is the workflow.

The problem

A model cannot work in your business until something gives it records, actions and limits, and building that yourself is the long part.

The model is rented by the month and gets better each quarter. The connectors, the joined data, the permissions and the log are yours to build and to keep working. These are brands on that work.

Months on a build of your own

“We were trying to build our own AI forecasting system. Fulfil launched their Claude integration, and it’s been way better than what we spent four months trying to build ourselves.”
Matt Orlić, CEO & Co-Founder, Qure Skincare

A developer between you and the tool

“The app I built had a working prototype in three weeks, because I was able to do it myself and not have to translate everything I needed to a developer, have that person build it or not build it, and then take another stab at it.”
Sam Alter, Founder, Atlas Pet Company

An agent is as good as the records under it

“The micro apps you use are only going to be as good as the data you have inside your ERP.”
Will Andrews, VP of Operations, Grunt Style
The harness

The harness is the part between the model and your business.

You choose the model, and you can change it. Your business is your channels, your warehouses and your bank. Fulfil is the part in the middle that both of them already work through.

Three parts You bring the first, and Fulfil is the second
Your AIThe model and the job
Claude, ChatGPT, Grok, OpenClawChat
Claude Code, Cursor, CodexTerminal
Your own agentCode
Your instructionsYour schedule
FulfilThe harness
RecordsOne set
ActionsThe product’s own
PermissionsEach person’s
ApprovalBefore a change
Audit trailEach write
Micro appsHosted
Your businessAlready connected to Fulfil
Shopify and marketplacesOrders
Warehouses and 3PLsInventory
Retailers, through EDIWholesale
Banks and cardsCash
The same connectionsyour team uses
1 address to paste1 sign-in0 API keys to create
Compare

This is what you build when you build your own, and what is already there on Fulfil.

Both ways use the same models. The difference is how much you build and keep working before an agent does its first useful job.

Building your own, over separate toolsBuilding on Fulfil
RecordsA connector for the store, each marketplace, each 3PL and the accounting system, and a database where you join them. Orders, inventory, fulfillment, EDI and accounting are already one set of records.
One numberEach tool keeps its own count and its own IDs. You write the rules that say which one is right. One count for each product, and the ledger is posted from the same record.
ActionsA tool to write and test for each action in each system. The actions of the product: create an order, post a journal entry, apply a payment, adjust inventory.
PermissionsAn API key for each system. What each person’s agent may do is yours to design. Each person signs in with their Fulfil login, and their agent has their permissions.
Approval and logA review step and a log across the systems, built by you. Write tools start off. Ask mode shows each change first. Each write is in the audit trail.
Tools for the teamHosting, sign-in and deploys for each dashboard or small app. Micro apps run inside Fulfil with the Fulfil login, a preview and a rollback.
UpkeepWhen a channel or a tool changes its API, your connector stops until somebody fixes it. Fulfil keeps the channel, 3PL and EDI connections working. They are the ones the product runs on.
What you buildThe harness first, then the workflow. The workflow: the instructions, the checks and the schedule for the job.

When a build of your own fits better

You are not changing your ERP

Fulfil is the harness because it is the system of record. If your orders and your ledger stay where they are, build over them.

The job is outside operations and accounting

Ad creative, support replies and product content read other systems. An agent for those needs little from an ERP.

You have engineers and unusual data

A team that already runs its own data platform may want the control of its own harness, and can still read Fulfil through the API.

What stays your work on Fulfil

Clean records

An agent repeats what the records say. Costs, lead times and counts must be right before you hand a job over.

The job description

Say what the job is, how it is done today and when to stop and ask, as you would to a new hire.

The model and the schedule

You pay for your assistant, and the schedule of a job runs there or in your own runner.

How to use it

Start with questions, and hand over a whole job last.

Each stage uses the same connection and the same permissions. Stay at one until you trust it.

1. Ask

Connect your assistant and only read.

Paste one address into Claude or ChatGPT and sign in. Write tools stay off. The team asks about orders, inventory and cash, and you see where the records are wrong.

Evereden’s operations team asks every hour

2. Act

Let it change records, with your approval.

Set the write tools to Ask. The assistant drafts the purchase orders or the bin changes, shows you each one and waits.

Atlas Pet Company moved its parts to a two-bin system this way

3. Build

Give a repeated job its own screen.

Describe the dashboard or the queue, and Claude builds it as a micro app on live records. Your team opens it with the Fulfil login.

Grunt Style built 25 micro apps in under 60 days

4. Hand over

Give an agent a job description and a schedule.

Write the job as you would for a new hire. Give the agent a user of its own with the permissions of that job, and run it from Claude Code on a schedule.

At Atlas Pet Company an agent has done this for about six months

Some jobs need no build at all. Fulfil has agents of its own for defined jobs, such as coding bank and card transactions, first in shadow mode and then up to an amount that you set. See the agents in Fulfil

A job handed over

At Atlas Pet Company, an agent named Kai does the work of a head of operations.

“So I took their job description, dumped it into Claude Code, and said: ‘This person’s gone. We need to replace them with an agent, and we need to build this into Fulfil and Claude Code so it’s all automated and scheduled.’”
Sam Alter, Founder, Atlas Pet Company

Atlas makes dog leashes and harnesses in Colorado with four full-time employees. Three people took the head of operations role and none stayed 90 days. Kai works through Fulfil MCP, and has for about six months. Sam gives his agents full access. That is his choice: on a new connection the write tools are off.

  • A customer writes at 1 a.m. to change an address. Kai holds the order, changes it and releases the shipment
  • When Kai cannot make a change, it flags the order and leaves it on hold for a person
  • An agent keeps the accounting in Fulfil up to date each day
Read the story of Atlas Pet Company
Atlas Pet Company leashes, collars and a harness Atlas Pet CompanyDog gear, made in Colorado
SO-20418Address change
1Hold the orderDone
2Change the addressDone
3Release the shipmentDone
3 changes, by the agent’s user3 lines in the audit trail
Customers

Operators build on Fulfil themselves.

Katie Powers of Caraway on a video call Katie PowersSenior Director of Accounting, Caraway
“So I’ve been able to build out a micro app within Fulfil that like refreshes and pulls in the real time balance sheet balances. And I can do what I was doing in Excel in this micro app.”
Will Andrews of Grunt Style Will AndrewsVP of Operations, Grunt Style
“I am not a developer. I’m just an operator with a passion for technology because it usually helps my people. In less than 60 days, I built an entire ecosystem my whole company is using.”
Erin of Cora on a video call ErinRetail Planning & Analysis, Cora
“I think Fulfil has really been good about enabling operators like ourselves to build what we see as useful.”

Results at other brands

Questions

How building on Fulfil works.

What is an AI harness?
A harness is everything around an AI model that lets it do work: the records it reads, the actions it may take, the permissions, the approval step, the log of what it did and the place where its tools run. The model reasons. The harness decides what it can see and do. For an ecommerce brand, Fulfil is the harness for orders, inventory, fulfillment and accounting.
Do I need developers to build AI workflows on Fulfil?
No. An operator connects Claude or another assistant with one address and one sign-in, and builds from there by describing the job. Grunt Style's VP of Operations built 25 micro apps in under 60 days with no developers. A developer or an agency can go further with the CLI and the API.
Which AI models and assistants can I use?
Any assistant that supports the Model Context Protocol, including Claude, ChatGPT, Grok and OpenClaw, connects through Fulfil MCP. An agent that runs shell commands, such as Claude Code, Cursor or Codex, uses the Fulfil CLI. Your own code uses the API. You can change the model and keep everything you built.
Can an agent run on a schedule with nobody at the keyboard?
Yes. The schedule lives in your assistant or in your own runner, for example a scheduled task in Claude or a job that starts Claude Code. For a job with no person signed in, give the agent a Fulfil user of its own with only the permissions the job needs, and connect it through the CLI or the API with that user's key. Its work is recorded under that user.
What can an agent change in Fulfil, and how do I limit it?
It can create orders, post journal entries, apply payments and adjust inventory, within the permissions of the user it signs in as. Write tools are off until you turn them on. In Ask mode the assistant shows each change and waits for you. An administrator chooses which permission sets may use MCP. Each write is in the audit trail with the user, the action and the time. A write is a real change and there is no undo, so read each approval.
When is building our own AI stack the better choice?
When you are not ready to change your ERP, when the job is outside operations and accounting (ad creative or support replies, for example), or when you have engineers and data that no product holds. If the job needs orders, inventory and the ledger to agree, most of a build of your own is joining those records, and that part is already done in Fulfil.

Works with Claude and the assistants you already use.

  • Claude
  • ChatGPT
  • Grok
  • OpenClaw
  • Your own agents

An agent reads the orders, the inventory, the purchase orders and the ledger that your team uses, with the permissions you set.

Example

Which orders older than 30 days have not shipped, and what should we do with each?

Nine orders, in three groups. Five wait for TWL-204, which arrives on the purchase order due Thursday. Three are wholesale orders on hold for credit. One has an address that the carrier rejected. I can draft the emails for the five, and I have left the hold on the other four for a person.

Answered from the same records that your team uses

On the shelf on the books.