Skip to content
← All projects
/ Case study · ERPSource reviewed · October 2026

ABAJ ERP

From incoming orders to stock and profit.

Creator · end-to-end2026Web · back office
View contribution & implementation evidence ↓
Web
Next.jsTypeScriptDrizzleTursoTailwind CSS
Web · back office

From incoming orders to stock and profit.

ABAJ ERP
Web

Designed and built by Alexanders Schwartzmann · end-to-end

  • Back-office UX & modules
  • Multi-channel order backend
  • Ingredient stock & recipes
  • COGS & accounting journal
View contribution & implementation evidence ↗
ABAJ ERPInteractive walkthrough

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

ABAJ ERP: Inspect orders across channels
Explore the product

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.

Original ERP shell & modules · isolated sample operations

1 / 4
ABAJ ERP · Inspect orders across channels
Interactive walkthrough using real product captures. Screen navigation stays in this portfolio.
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

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.
Inspired by ABAJ ERP?

Let’s build around your workflow.

Discuss a similar project
Contribution & implementation

I designed and built this project end to end.

Project creator

Alexanders Schwartzmann

From product design, UX, and architecture to the feature implementation 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

Implementation evidence

The implemented feature, how it works, and the technical decision behind it.

01 / Original screen & source

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 / Original screen & source

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.

Evidence scope

The original ERP modules render isolated sample operations. The figures are examples; no private financial records or production writes are used.

Original ERP shell & modules · isolated sample operations ·

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.