Posable Office

Prototypes and design explorations

Invoice (Back-Office)

The chosen design: list pages, New / Edit as steps in the footer, Add Items, serial and batch pages, and the order / invoice view pages with the whole approval lifecycle to try

Print & E-mail Formats

What the customer receives: the A4 sheet and the e-mail for a Sales Order and a Sales Invoice, in every status — draft, approval pending, rejected, approved, completed, voided, returned

Purchase Print & E-mail Formats

The buying side: Purchase Order, Goods Received Note and Purchase Return — the A4 sheet and the e-mail, in every status

Print Options — selling side

Choose what the printed order / invoice includes (logo, sales rep, barcode, prices, QR, signatures…) with the A4 sheet updating as you tick; save as the store default

Print Options — buying side

The same choices for a Purchase Order, Goods Received Note and Purchase Return; flip the document from the top bar

Implementation Plan

Revision 48: the target lifecycle (§2.1a), the status log (§2.1b), the colour standard (§6.3a), every target screen (§6.5) and the open gaps grouped for review

Return (Back-Office)

Sales Return — Mockup

Same layout as the invoice: Return Items on a completed invoice, the step form (Invoice & Items, Refund, Review) with Back to stock or Write off per item, a reason per item, and the return view page with the approval lifecycle, Print and Send Email

Credit Invoice — Print with Options

The invoice's print page for a credit invoice: choose what goes on the paper, live A4 preview, copies, remark and company default

Credit Invoice — Print & E-mail

The printed credit invoice on A4 and the e-mail the customer gets, Completed and Voided

Implementation Plan

Revision 3: database review of every return table and column, a reason and Back to stock or Write off per item, Invoice and Items on one step, print and e-mail the same as the invoice, and the decisions for the owner (§9A)

Purchase Return (Back-Office)

Purchase Return — Mockup

Mockup of the Purchase Return screens in the back-office

Mall Integrations (Back-Office)

Mall Integrations — Mockup (steps v4)

The latest design: every step fits the screen with no scrolling. Stores & mall, Delivery, File and Preview, in plain words — try New, View, Edit and a Manual (Others) integration

Mall Integrations — previous version (steps v3)

Kept for comparison: the same four steps before the fit-to-screen redesign

3rd Integration Log

Where each integration’s runs are kept: View Logs opens it unfiltered, and Logs on a Mall Integrations row opens it filtered to that integration

Code Map (graphify)

Code Map — Graph

Interactive map of v2-sellable-bo, v2-sellable-api and db-postgresql (code only): 44,497 items in 1,044 groups. Built 5 Oct 2026

Return of a POS (POPC) Sale (Back-Office)

Plan v3 — Return of a POS (POPC) Sale in BO: rules, End Shift, store

Rules for BO returns of POS (POPC) sales, the sync error, End Shift cash and card totals, how the credit invoice looks in POS (POPC), and which store it belongs to. Reviewed, for your decisions, 13 Oct 2026

Plan B — BO does not return POS (POPC) sales

The small plan: BO returns only BO-made sales, POS (POPC) sales are returned at POS (POPC). Two-line switch, no cash rules, no new POS build. Compare with Plan v3, 14 Oct 2026

Online Store Business Day (Back-Office)

Proposal — Business Day for an Online Store

Open and close time in store settings, sales only inside the hours, one day and shift per day with no register. Options, what changes in the code, and 8 decisions for you. Draft 2, reviewed, 15 Oct 2026

E-Invoice (Back-Office)

Current design — E-Invoice page today

One page, Finance > E-Invoice, with 3 tabs: Configuration, Consolidation, Submission. Detail pages, setup wizard and store setup. Copied from the real app, 19 Oct 2026

New design — 3 separate menu pages

Finance > E-Invoice > Configuration, Consolidation, Submission. Each page has its own link and access right. Same columns and buttons as today. Reviewed, 19 Oct 2026

Write-up — what changes and why

Decisions, code that changes when built, known limits

Plan — Sending method: Our system or External system

Each company picks who sends e-invoices to LHDN. External: no TIN needed, the other system writes results into Sellable. 14 decisions, files, order, access rights, hand-over list. Draft 2, reviewed 2 rounds, 19 Oct 2026

POS Client (POPC) — Bug Analysis & Fix Plan

Deposit Missing from End Shift — Revised Plan

Draft, 23 Oct 2026. Dev check: a deposit in the same shift is already counted. Main suspect is a top-up taken in a later shift. Step 0 is to reproduce it in the app; the fix (a shift on each payment) is only built if it shows.

Audit of the first plan — why it was withdrawn

Four checks against the real code and database. Verdict: not ready

Earlier deposit bugs — already fixed

Order locked after a full deposit, button colours, gift cards, rounding

E-Invoice Flow Review (POS / API / BO / CRM)

Report — why status is stuck, and what a void or return does

LHDN send and status job are switched off. Void and return do not touch the e-invoice. How others handle it, and a fix plan. 23 Oct 2026