Skip to content
← All projects
/ Case study · Web · back office

ABAJ ERP

From incoming orders to stock and profit.

Orders from 6 sales channels in one back office

ABAJ ERPInspect orders across channelsInspect orders across channels01 / 04
For developers
Web
Next.jsTypeScriptDrizzleTursoTailwind CSS
What I did & the proof ↓
Web
ABAJ ERPProduct tour

Follow the back office: inspect incoming orders, check ingredients and stock movements, then read profit and the journal.

ABAJ ERP: Inspect orders across channels
Screen by screen

Inspect orders across channels

The order queue brings delivery, pickup, dine-in, takeaway, reservations, and catering together with status and date filters. Operational records are samples.

Real ERP modules · sample data

1 / 4
ABAJ ERP · Inspect orders across channels
Real product screenshots. Everything you click stays inside this portfolio.
The problem
Orders, ingredient stock, and financial records need a shared operational view.
What I built
A back office for six sales channels, inventory movements, COGS, profit, and accounting journals.
What it enables
The team can trace incoming orders, check ingredients, and read the financial picture together.
Feature highlights
  • Orders across six sales channels
  • Ingredients, stock & inventory ledger
  • Revenue, COGS & debit/credit journal
Built with

Next.js / TypeScript / Drizzle / Turso / Tailwind CSS

Designed and built by Alexanders Schwartzmann · start to finish

  • Back-office UX & modules
  • Multi-channel order backend
  • Ingredient stock & recipes
  • COGS & accounting journal
See what I did and the proof ↗
Want something like ABAJ ERP?

I can build one around how your business works.

Talk about a similar project
What I did

I designed and built this project from start to finish.

Project creator

Alexanders Schwartzmann

From the product idea and design to the code behind the features below.

My implementation scope
  • Back-office UX & modules
  • Multi-channel order backend
  • Ingredient stock & recipes
  • COGS & accounting journal

How the main flow works

  1. 01

    Orders across sales channels

  2. 02

    Recipe quantities & ingredient costs

  3. 03

    Paid-order journal posting

  4. 04

    Revenue, COGS & profit reports

Proof of the work

What was built, how it works, and why it was built that way.

01 / Real screen & code

Inventory with an operational ledger

The inventory module tracks units, ingredient costs, stock quantity, and movements for each outlet.

Technical decision

Movement records explain how stock changes; a current stock number alone cannot explain its origin.

02 / Real screen & code

Recipe cost becomes an accounting entry

The ledger source calculates order COGS from recipe quantities and ingredient costs, then posts debit and credit rows for a paid order.

Technical decision

Journal posting checks the order reference before adding rows, so a repeated request does not post the same order again.

About these screens

Screens from the real ERP modules with sample data. The numbers are examples; no private finances were used and nothing was changed in the live system.

Real ERP modules · sample data ·

Core purpose

Follow the back office: inspect incoming orders, check ingredients and stock movements, then read profit and the journal.

Feature highlights

  • Orders across six sales channels
  • Ingredients, stock & inventory ledger
  • Revenue, COGS & debit/credit journal

The walkthrough

Inspect orders across channels

The order queue brings delivery, pickup, dine-in, takeaway, reservations, and catering together with status and date filters. Operational records are samples.

Check ingredients & stock

The actual inventory module shows ingredient units, unit cost, and available quantity per outlet. Low stock is highlighted so the operator can spot it.

Trace stock movements

Read the stock ledger to distinguish usage from sales and additions from purchases, with ingredient, outlet, and quantity on each row.

Read profit & the journal

The finance module shows net revenue, cost of goods sold, gross profit, and margin above the transaction’s debit/credit journal. These are example figures.

Source and preview scope

Original ERP shell & modules · isolated sample operations. Captured on 13 October 2026. Screen navigation stays within this portfolio.