PRODUCT · ERP

One ERP for the whole wholesale business. Claude built in next.

We designed and built a complete ERP for StrictlyEcig — sales, purchasing, inventory, finance and fulfilment in one connected system. Version 1.0 is complete. Next, we are building Claude into every screen as an assistant that answers from your own data and prepares the work for you to approve.

ERP v1.0 — complete
Claude assistant — in development
Book a demoSee how Claude fits in
StrictlyEcig ERP · v1.0
Search orders, ledger, stock...Ctrl F
Concept preview
Assistant Panel Open
Open Wholesale Orders
38 orders
Single Source Stock
Real-time
Active Ledgers
Balanced
A/R Ageing — open invoicesOverdue > 60 days
Invoice #CustomerBalanceDays overdue
INV-1849Apex Smoke LLC$24,100.0074 days
INV-1848Coastal Vapes Inc$15,350.0068 days
INV-1847Metro Wholesale$8,800.0062 days
Claude Assistant
In development · Top-bar & keyboard trigger
Screen Context: A/R Ageing
“Which customers are more than 60 days overdue, and how much do they owe in total?”
Tool executed: query_ar_ageing(days: 60) (User permissions checked)

Found 3 customers with balances overdue > 60 days totaling $48,250.00:

  • Apex Smoke LLC: $24,100.00 (74 days) — View Statement
  • Coastal Vapes Inc: $15,350.00 (68 days) — View Statement
  • Metro Wholesale: $8,800.00 (62 days) — View Statement
Read-only query
Strict server permission check: Claude can never view or act beyond your assigned role.
THE PROBLEM

Three systems, five-minute syncs, oversold stock.

StrictlyEcig relied on three separate systems: SAP Business One, Magento, and an in-house purchasing tool. Those three synced orders and stock on 5-minute timers across three order channels — the sales team, the web store, and dropship — which caused overselling. The new ERP replaces all three with one real-time source of truth: every channel reads and writes the same stock in real time. The customer storefront connects directly through a dedicated API, and the ERP database is the only database.

Before (Three Disconnected Systems)
SAP Business One + Magento + custom tool syncing on 5-minute timers across sales team, web store, and dropship channels — causing overselling.
Now (One Single Source of Truth)
One real-time ERP database where every order channel reads and writes stock synchronously with row locks. No sync timers. Two orders cannot take the same unit.
14
Modules
92
Screens
138
Database tables
261
Permissions
28
API endpoints
596
Automated tests
MODULES

14 connected modules. One unified platform.

Every operational capability wholesale distribution requires, built natively into a single architecture.

01

Dashboard

Live revenue, orders, customers, low-stock alerts; dashboard templates per role.

02

Sales (A/R)

Quotations, sales orders, A/R invoices, credit memos, tax after discount, PDF documents with barcodes, e-mail of documents.

03

Purchasing (A/P)

Purchase orders, goods receipt with landed cost, A/P invoices, A/P credit memos.

04

Inventory

Items, groups, price lists and special prices, multiple warehouses and bins, transfers, goods issue/receipt, stock counts, revaluation, batches and expiry dates, an append-only stock ledger.

05

Business Partners

Customers and vendors, customer groups, compliance documents (licences) with expiry, billing and transaction history.

06

Financials

Chart of accounts, double-entry journal entries, reconciliation, opening balances, trial balance, profit & loss, balance sheet, cash flow, fiscal periods and year-end close.

07

Payments

Incoming and outgoing payments, A/R and A/P ledgers, a card-payment gateway adapter (authorise, capture, void, refund).

08

CRM

Leads, pipeline, activities and reminders.

09

Pick & Pack

Pick lists, packing, shipments, printable pick sheets.

10

HR & Users

Users with e-mailed invitations, employees, departments, roles and permissions, two-factor sign-in.

11

Reports

Saved reports per area, scheduled P&L reports by e-mail.

12

Integrations

Connector framework for payment, shipping, e-mail marketing, helpdesk, messaging and dropship services; webhooks out.

13

Administration

Company settings, document numbering, tax rules, promotions, shipping restrictions, a shared rules engine, alerts, unified audit logging, media library, data import.

14

Web Module

Storefront content (pages, menus, brands, blog, banners, newsletter, lab reports) and the storefront API.

ARCHITECTURE

Built on solid ground.

Core decisions that keep every transaction immutable and the ledger intact.

Real double-entry accounting

Every document posts a balanced journal entry; posted entries are never edited or deleted, only reversed.

Append-only stock ledger

Stock totals updated in the same database transaction with row locks, so two orders cannot sell the same unit.

Exact decimal money

Money stored as exact decimals (never floating point), rounded to the cent in one place.

Tied inventory valuation

Inventory value ties to the general ledger to the cent, checked after every change.

Unified audit log

A single audit log records every field change with who, when and from where (screen, API, system, integration).

Shared rules engine

One shared rules engine drives tax, shipping restrictions, promotions and alerts.

PostgreSQL background job queue

Background job queue (on PostgreSQL) for e-mail, alerts, reminders and scheduled reports, so no integration blocks a save or a checkout.

Security and governance

Full security audit before release, role-based permissions, 2FA, hashed session and reset tokens, strict security headers with a content security policy, rate-limited password resets.

Technology Foundation:Next.js · React · TypeScript · PostgreSQL · Drizzle ORM · Tailwind CSS
ASSISTANT IN DEVELOPMENT

An assistant that lives inside your ERP.

After v1.0 ships, we build a version of the ERP with Claude built in: an assistant panel available on every screen, the way assistants now live inside document and e-mail software. Staff ask in plain English; Claude answers from the company's own live data, explains what is on the screen, and prepares work (drafts) for a person to review and approve. It is not a separate chatbot: it works inside the ERP, with the signed-in user's permissions.

ARCHITECTURE

How it works.

System Architecture Flow
01 · TRIGGER
User on Screen
Top-bar button or a keyboard shortcut opens the panel.
02 · API CALL
Claude Tool Use
Server passes structured ERP action queries via Anthropic API.
03 · SECURITY
User Role Checks
Tool execution runs under signed-in user's 261 RBAC permissions.
04 · DRAFTS ONLY
Human in the Loop
Write tools only prepare drafts; person reviews and posts.
05 · AUDIT LOG
Source: “assistant”
Suggestion and approval fully logged alongside screen and API actions.
Side Branch A: Background Queue
Longer jobs (overnight collections summaries, month-end checklists) run asynchronously on PostgreSQL worker queue.
Side Branch B: MCP Server (Later)
Future MCP server enables team members to connect desktop Claude apps directly with strict API permission scopes.
Step 1

Screen context

The user opens the assistant panel on any screen (button in the top bar plus a keyboard shortcut). The current screen and record are passed as context.

Step 2

Anthropic tool use

The ERP server calls Claude through Anthropic's API using tool use. Each tool is an existing, already-tested ERP server action or report query (for example 'find overdue invoices', 'stock on hand for item X', 'draft a purchase order').

Step 3

User role check

Every tool runs as the signed-in user, through the same 261-permission role check as the screens. Claude can never see or do more than that user can.

Step 4

Drafts only (human in the loop)

Read tools answer questions. Write tools only create drafts (draft order, draft PO, draft journal entry, draft e-mail, draft rule). A person reviews and presses the real Post / Send button. Claude never posts to the ledger, moves stock, takes a payment or sends an e-mail by itself.

Step 5

Audited as "assistant"

Every assistant action is written to the existing audit log with a new source, "assistant", next to screen / API / system / integration, so finance can see exactly what was suggested, by whom it was approved, and when.

Step 6

Background queue

Longer jobs (overnight collections summary, month-end review) run as background jobs on the ERP's existing job queue.

Step 7

MCP server (later)

Later: an MCP server for the ERP, so a client's team can connect their ERP to Claude's own apps with the same permission scopes as the API keys.

Model Strategy: A fast Claude model for quick lookups and classification, and a stronger Claude model for analysis and multi-step drafting. Prompt caching for the large, slow-changing context (chart of accounts, item catalogue, rules).
USE CASES

What Claude will do.

All modules
“How do I receive a shipment with freight cost spread over the items?”

Claude explains the steps for the screen the user is on, using the ERP's own documentation.

Read-only
Reports, Financials
“Which customers are more than 60 days overdue, and how much do they owe in total?”

Claude runs the A/R ageing query and answers with the list and a link to each customer.

Read-only
Sales
“Make an order from this e-mail”

Claude matches the products and the customer's price list and builds a draft sales order.

You approve: the draft order
Purchasing, Inventory
“What should I reorder from this vendor this week?”

Claude looks at stock on hand, stock on order, sales speed and expiry dates, and drafts a purchase order with its reasons per line.

You approve: the draft PO
Payments, Business Partners
“Draft polite reminders for everyone overdue more than 30 days”

One personalised draft e-mail per customer with their open invoices attached.

You approve: each e-mail
Financials
“Anything unusual before I close September?”

Claude reviews journal entries, unreconciled items and unusual amounts, and writes a checklist with links.

Read-only
Administration
“10% off group Disposables for wholesale tier B customers in Texas, until the end of the month”

Claude builds a draft promotion in the rules engine and shows exactly which conditions it set.

You approve: the rule
Data Import
“Here is our old customer export”

Claude maps the unknown columns to the right importer and runs a dry run (the importer's dry run changes nothing).

You approve: the real import
Business Partners
“Whose licences expire in the next 30 days?”

List plus draft renewal-request e-mails.

You approve: the e-mails
Dashboard, Reports
“Why is gross margin down this month?”

Claude breaks the change down by item group, customer and cost changes, with the figures it used.

Read-only
PRINCIPLES

Trust by design.

Human in the loop

Claude prepares, people approve. Nothing posts on its own.

Server-enforced permissions

Same permissions as the user, enforced on the server, not in the prompt.

Full audit trail

Full audit trail of every suggestion and approval.

Data isolation and privacy

Only the data a question needs is sent; each client has its own database.

Immutable accounting integrity

The accounting rules do not change: posted entries stay immutable, stock and ledger stay tied to the cent.

We already build with Claude.

Claude Code is part of our everyday engineering on this ERP: implementing modules, writing and running tests, reviewing code and auditing security. Building the assistant on Claude is the natural next step for us.

ROADMAP

The path from ERP v1.0 to in-app intelligence.

Now

ERP v1.0 complete, final QA

Claude Code already part of how we build and test it.

Step 1

In-app help assistant

Read-only, documentation and screen context.

Step 2

"Ask your business"

Read-only data tools under the user's permissions.

Step 3

Drafting tools with approval

Orders, POs, e-mails, rules, logged as "assistant".

Step 4

Background agents & MCP server

Background agents (collections, month-end review) and an MCP server for the ERP.

FAQ

Frequently asked questions.

No. The ERP itself is complete (v1.0). The Claude assistant is in development; this page describes what we are building.
GET STARTED

Ready to see the platform in action?

Book a demo and we will walk you through the StrictlyEcig ERP.

Book a demo

Claude is a trademark of Anthropic, PBC. Byte Busters is an independent company and is not affiliated with or endorsed by Anthropic.

Idea → Reality