NastyCookie ERP

Displays all SKUs with on-hand, allocated, and available quantities grouped by product. Drill down to see per-location breakdowns including batch and lot numbers.

Row Colour Coding & Sort Priority

Inventory rows are automatically sorted and colour-coded by urgency. Higher-priority rows always appear above lower-priority ones.

The product catalogue. Every item in the warehouse must have an SKU record. SKU codes are auto-generated by category prefix:

• RM-xxxx — Raw Materials
• FG-xxxx — Finished Goods
• PK-xxxx — Packaging
• WP-xxxx — Work In Progress

Each SKU stores minimum stock, reorder point, cost per unit, selling price, storage type (ambient/refrigerated/frozen), and halal certification expiry.

Picking lists are auto-generated when a Sales Order is approved. They guide warehouse staff to pick the right quantities from the right locations.

Defines warehouse bins and racks. Each location belongs to a zone (A, B, C, FG, Cold) and has a capacity in kg. Stock is tracked per-location for precise inventory control.

Conduct a physical count of actual stock. After counting, the system shows variances between system quantity and physical count. A manager must approve variances before they are applied.

1. 1Click New Stock Count and select the scope (full warehouse or specific zone).
2. 2Warehouse staff physically counts items and enters quantities.
3. 3System highlights discrepancies in red.
4. 4Manager reviews and approves — system adjusts inventory accordingly.

Raise purchase orders to buy materials from suppliers. POs go through an approval workflow before being sent.

Creating a PO

1. 1Go to Inbound → Purchase Orders → New PO.
2. 2Select supplier and expected delivery date.
3. 3Add line items (SKU, quantity, unit price).
4. 4Save as Draft or Submit for approval.
5. 5A manager approves and marks as Sent to supplier.

When goods arrive, raise a Goods Receipt Note (GRN) against the approved PO. Received items are added to warehouse stock automatically.

1. 1Go to Warehouse → Goods Receiving and find the corresponding PO.
2. 2Enter received quantities (may differ from ordered).
3. 3Enter batch numbers and expiry dates for traceable items.
4. 4Post the GRN — stock levels update immediately.

Items that fail inspection at goods receiving are placed on QC Hold. They cannot be used in production or sold until released or rejected.

• Release — item passes QC, returned to available stock
• Reject — item fails QC, triggers supplier return process

Send price quotes to customers before committing to a sale. Quotations can be converted directly into Sales Orders when accepted.

Confirmed orders from customers. Approving an SO triggers automatic stock reservation (FIFO allocation) and picking list generation.

The dispatch page uses a two-panel layout:

• Left panel — Staged Queue: SOs where picking is complete and goods are ready to ship. Tick one or more SOs to include in a dispatch run.
• Right panel — Dispatch Plans: Created dispatch plans showing driver, vehicle, and linked SOs. Click Mark All Delivered to complete a run.

1. 1Select one or more staged orders on the left.
2. 2Click Create Dispatch Plan, enter driver and vehicle details.
3. 3When goods are delivered, click Mark All Delivered — all linked SOs advance to Delivered and invoices are created.

Log returned goods from customers. Returns are reviewed and either restocked (good condition) or written off (damaged). Credit notes are generated automatically.

The Production Overview is the daily command centre. It shows live KPI cards and four real-time activity panels that surface items requiring immediate attention.

Activity Panels

• Active Jobs — running scheduler jobs with quick link to Scheduler.
• Awaiting QC — batches pending quality inspection with quick link to Production QC.
• Ingredient Requests — pending or partially fulfilled ingredient requests with quick link to that page.
• Finished Goods Pending — QC-passed batches not yet transferred to Warehouse with quick link to Finished Goods.

Rooms are the physical production spaces where work happens. Each Room Template defines a space that the Scheduler can book. Rooms must be configured before any jobs can be scheduled.

Manpower Templates define categories of labour used in production (e.g. Baker, Mixer Operator, Packer). They are not individual people — individual workers are registered separately in Production Users.

A Job Template is a reusable production blueprint. It links an approved recipe to an ordered sequence of processes, each assigned to a room type and manpower type. The Scheduler uses Job Templates to pre-fill all job settings when a new run is inserted.

Register individual production workers and assign them skills. The Scheduler uses skills to validate that workers assigned to a process are qualified for it.

Production Users (left panel)

• Each worker has a name, employee ID, and one or more assigned skills.
• Filter workers by skill using the dropdown in the search bar to quickly identify qualified staff for a given process.
• Inactive workers are hidden from the Scheduler's manpower assignment panel.

Skills (right panel)

• Skills are defined here (e.g. "Chocolate Mixing", "Oven Operation", "Packaging Machine").
• Click a skill to toggle assignment for the selected worker. Skills can also be assigned by drag-and-drop onto a worker card.
• Skills are immediately reflected in the Scheduler without a page reload.

The Scheduler is the operational heart of the Production module. It presents a drag-and-drop weekly timeline where jobs are placed into time slots against rooms and manpower. Each week is saved as a named schedule and persists until overwritten.

Layout

Scheduling a Job — Step by Step

1. 1Click Insert Job in the Job Queue panel. Select a Job Template and set the number of batches for this run.
2. 2The job card appears in the queue showing expected duration and ingredient summary drawn from the template's linked recipe.
3. 3Drag the job card onto the timeline at the desired start time and room row.
4. 4Click the placed job block to open its detail panel. Assign workers whose skills match each process requirement.
5. 5Click Save Schedule. The week's schedule is persisted and immediately visible to all production staff.

Job Lifecycle

Time Settings

Click the Time Settings (clock) button to configure the factory's working-hours window. Default: 08:00–17:30. The timeline enforces this window and will visually flag jobs placed outside it.

Undo

The Undo button reverses the last drag action on the timeline. It is only active before saving — it cannot undo a saved schedule.

Schedule Views are read-only visualisations of the current week's saved schedule in three formats. Use these for shift briefings, management reporting, and sharing with staff who do not need edit access to the Scheduler.

Ingredient Requests are the formal mechanism by which Production requisitions raw materials from the Warehouse. Stock does not move until the request is approved and fulfilled by the Warehouse team.

Key Rules

• Each request is linked to a scheduled job so ingredient consumption is traceable per batch.
• Partial fulfilment is supported — Warehouse can deliver part of the request now and mark the remainder pending.
• Raw materials on QC Hold in the Warehouse cannot be transferred to Production until QC releases them.
• The Production Overview's Ingredient Requests panel shows all pending requests in real time.

Production maintains its own inventory ledger — separate from the main Warehouse — covering raw materials, packaging, and finished goods physically held in the production facility. It has three tabs:

Live Stock Tab

Filter by category (Raw Material / Finished Good / Packaging) or search by SKU / product name.

Inventory Count Tab

Conduct a physical count of production stock. Staff enters actual quantities; the system calculates variance against the system figure. A variance summary appears in the header before submission.

1. 1Enter actual physical counts in the Actual Count column for each SKU line.
2. 2System calculates variance (actual − system). Negative = missing stock; positive = surplus.
3. 3Add notes for any lines with significant variance.
4. 4Click Submit Count to commit adjustments. Production Inventory levels update immediately.

Count History Tab

Full audit trail of all past production inventory counts: Count #, Date, Items counted, Net Variance, Status, Type, and who submitted it.

After a batch finishes production it moves to QC before the output can enter Finished Goods. This gate prevents substandard product from reaching the Warehouse or customers.

QC Statuses

QC Table Columns

Batch #, Recipe, Planned Qty, Actual Qty, Batch Status, QC Status, Actions. The Planned vs Actual Qty gap is the primary quality signal — a large discrepancy indicates waste, a recipe deviation, or a weighing error that should be investigated before passing.

Finished Goods is a holding ledger for QC-passed batches that are ready to be transferred to the Warehouse but have not yet been handed over. Think of it as the production side of the transfer waiting room.

• Each entry shows recipe, batch number, quantity produced, and production date.
• Items here do not appear in Warehouse inventory and cannot be allocated to Sales Orders.
• To move stock to the Warehouse, use Production In/Out → Out.
• The Production Overview's "Finished Goods Pending" panel surfaces unshipped items — monitor this daily to prevent expiry of perishable products.

Production In/Out is the transfer gateway between the Production and Warehouse modules. It handles both directions of stock movement and provides a full audit trail for every transfer.

In — Inbound Receipts

Records raw materials physically arriving into the production facility from the Warehouse (fulfilling an approved Ingredient Request).

1. 1Warehouse dispatches ingredients against an approved Ingredient Request; status moves to "Dispatched".
2. 2Production sees the pending receipt here under the Pending Receipt filter.
3. 3Production opens the receipt modal, verifies expected vs actually received quantities per ingredient line, and adds notes for any discrepancy.
4. 4Production confirms receipt — Production Inventory is updated (ingredients move from "Expecting" to "Existing").

Out — Transfer to Warehouse

Records Finished Goods being handed from Production to the Warehouse. This is the exact moment products enter Warehouse inventory and become available for Sales Orders.

1. 1Production initiates a transfer for one or more Finished Goods batches (from the Out tab).
2. 2Status changes to Dispatched — Awaiting Warehouse; Warehouse is notified.
3. 3Warehouse receives goods physically, confirms quantities in their module, and marks Received.
4. 4Warehouse inventory is updated — Finished Goods SKU is now available for Sales Orders and Dispatch.

The Costing sub-module calculates the total cost of each production batch. Results feed into Finance for COGS reporting and can be compared against selling prices (from the SKU Master) for margin analysis.

Complete sequence from initial setup through to finished product available for sale.

1. 1One-time setup: Configure Room Templates (production spaces), Manpower Templates (labour categories), register Production Users and assign their skills.
2. 2Recipe approved: Management approves the recipe version under Management → Recipes (Restricted). An unapproved recipe blocks Job Template creation.
3. 3Job Template created: Link the approved recipe to an ordered process sequence (rooms + manpower types). Set default batch size and per-process durations.
4. 4Ingredient availability check: Review Production Inventory → Live Stock. If insufficient raw materials are on hand, raise an Ingredient Request against the Warehouse.
5. 5Ingredient Request fulfilled: Warehouse approves and delivers. Production confirms receipt in Production In/Out → In. Ingredients move from "Expecting" to "Existing" in Production Inventory.
6. 6Job scheduled: In Production Scheduler, click Insert Job → select the template → drag onto the timeline → assign workers → Save Schedule.
7. 7Production runs: Batch status advances to In Progress. Production staff use Schedule Views (Room View / User View) for shift-level instructions.
8. 8Batch completes → QC: Status changes to Awaiting QC. QC officer records checks in Production QC and marks Pass, Fail, or Rework. Failed batches are written off; rework batches re-enter the Scheduler.
9. 9QC Passed → Finished Goods: Batch appears in Finished Goods as a pending transfer. Costing is calculated automatically at this point.
10. 10Transfer to Warehouse: Production initiates the transfer via Production In/Out → Out. Status changes to Dispatched.
11. 11Warehouse receives: Warehouse confirms quantities and marks the transfer Received. Finished Goods SKU is added to Warehouse inventory.
12. 12Available for sale: Warehouse inventory is live — the product can now be allocated to Sales Orders and dispatched to customers via the Outbound module.

Bank Reconciliation works on monthly periods. Each period holds uploaded bank statement transactions, per-category reconciliation state, parked entries, and journal adjustments. Periods can be re-opened until explicitly locked.

1. 1Create a period — Finance → Bank Reconciliation → New Period. Select month and year.
2. 2Upload bank statement — Click Upload Statement. Accepts CSV or Excel. The system auto-categorises each transaction row by description keyword (e.g. "ALLINPAY" → Kpay, "GPAY" → Grab).
3. 3Reconcile by category — Click each category tile. The right panel shows the matching logic and lets you mark the category reconciled once the difference is zero.
4. 4Park exceptions — For transactions that cannot be matched, create a Parked Entry. Optionally flag it as an Independent Journal Entry so it is included in the export regardless of park state.
5. 5Journal adjustments — Add standalone journal entries (debit/credit pairs) for items like bank charges, interest, or corrections that have no corresponding bank transaction.
6. 6Lock period — Once all categories reconcile and the comparison totals show zero difference, click Complete Period. This prevents further edits.
7. 7Export journal entries — Click Create Journal Entries to download a CSV of all adjustments for the period for posting into your accounting system.

Each category has its own matching logic. Understanding the rules prevents reconciliation errors.

Grab

Bank transactions identified by GPAY / GRAY NETWORK / FAST GRAY keywords. Matching is sum-based by outlet UID — the bank payout for a given outlet UID must equal the sum of all Grab system amounts for that outlet's UID. Outlet UIDs are mapped to locations (Marina Square → 65383, Orchard Gateway → 33861, Vivo → 80569). Category completes when every outlet UID's bank sum matches its Grab sum.

Kpay (Allinpay)

Bank transactions identified by ALLINPAY keyword. Matching is session-based by outlet name — each bank transaction is matched to a Kpay session with the same outlet and a close amount. Multiple sessions per outlet are possible. Category completes when all bank transactions are matched to sessions with zero unmatched remainder.

Foodpanda

Bank transactions identified by DELIVERY HERO / FOODPANDA keywords. Matching is per-outlet session — each Foodpanda payout references a 4-character outlet code (GEYA = Marina Square, EL8T = Orchard Gateway, LTR0 = Vivo, B7PL = Westgate). Each payout is matched to the Foodpanda system records for that outlet code. Category completes when every payout is matched.

Tabsquare

Bank transactions identified by ADYEN keyword. Matching is month sum-based — the sum of all Tabsquare bank payouts for the period must equal the total Tabsquare system report for the month. No per-outlet breakdown. Single difference check.

Shopback

Bank transactions identified by SHOPBACK keyword. Matching is total sum — the sum of all Shopback bank transactions must equal the total Shopback system report for the period. Single difference check.

Cash Deposit

Bank transactions identified by CASH DEPOSIT / CASH DEP / CDM keywords. Matching is individual checkbox — each cash deposit transaction must be manually checked off against a corresponding outlet cash count record. All transactions must be matched (checked) for the category to complete.

Svc Chg (Service Charges)

Bank transactions identified by SERVICE CHARGE / SVC CHG / SC / BANK CHARGE / BK CHG keywords. These are bank fees and charges — no reconciliation required. The category auto-completes. Transactions are listed for reference only.

Others

Any transaction not matched by the above keyword rules falls into Others. These are handled manually: create a journal entry for each unmatched item, selecting the correct account code (debit/credit). The category can be marked complete even if the running difference is non-zero, because Others uses journal entries as the authoritative record rather than a sum match.

Deliveroo

Bank transactions identified by DELIVEROO keyword. Matching works similarly to Foodpanda — each payout is matched to the Deliveroo system report for the corresponding outlet and period.

Parked entries are temporary holding records for transactions that need follow-up before they can be reconciled. They are per-category and per-period.

When a parked entry is resolved, click Unpark — the entry is removed and the running difference in the category updates immediately. Parked entries with Independent JE checked persist in the journal adjustment log even after unparking.

Journal adjustments are standalone double-entry records that are always included in the period's journal export. Unlike parked entries they are not tied to a specific bank transaction.

Use cases: bank interest income, bank charges not categorised above, rounding adjustments, contra entries for prior-period corrections.

Each entry requires: Date, Description, Account Code, Debit amount, Credit amount. The entry is saved permanently and survives park/unpark cycles in the same period.

The Finance module provides a read-only view of all invoices in the system. Supplier invoices (AP) are created when a GRN is posted. Customer invoices (AR) are created when a Delivery Order is marked delivered.

Full invoice editing (amounts, line items) is done in Inbound → Supplier Invoices and Outbound → Customer Invoices respectively. The Finance view is for payment tracking and overview.

🛒 Purchase-to-Pay (P2P)

📦 Order-to-Cash (O2C)

🏭 Production Cycle