e-Invoicing handled once a month, not per sale: counter sales consolidate into one summary e-invoice at month end (LHDN-permitted for B2C) — Shopee is excluded, since the marketplace issues its own e-invoice and its monthly figures are entered separately below.
Project Gaia — static mockup in Filament v3 idiom. No backend. Retail module; customer data shared with OEM underneath (channel-flagged), screens separated. Stock ships FEFO from FG with lots, same engine as OEM sales; the Double Root RM 5–8 band is the founder's real example.
Retail sales — field manifest
Field
Filament component
Type
Source
FK target
Sale # / lines
RetailSaleResource + Repeater
doc + lines
stored: retail_sales, retail_sale_lines (variant, qty, price, batch_id FEFO-picked); own RS- numbering series, separate from OEM SO series
variants / batches
Customer
Select (scoped) or Walk-in
FK nullable
stored: customers — ONE table shared with OEM, channel enum (oem / retail / both); this select is scoped to channel ∈ {retail, both}
customers
Payment
Badge + Action
enum Cash/Transfer/Unpaid
stored: retail_sales.payment_status, .due_date
—
e-Invoice
Badge, derived
enum
open → "{month} consolidated ✓" once the month-end consolidation run is posted; B2B flag exports that sale individually
SAME variant_prices + sale-history tables — retail and OEM share one memory and one floor
variant_prices
Today strip (Cash / Transfer / Unpaid)
StatsOverview widget, derived
aggregate
Cash / Transfer: sum of today's retail_sales by payment_status; Unpaid total: the running AR balance across ALL unpaid retail_sales (not just today) — same figure as Retail > CRM "Owing" and Insights > Retail
retail_sales
Shopee — monthly channel entry
Card + stub Action
form (not built)
writes: channel_entries (month, channel='shopee', per-SKU qty, one revenue figure) → posts one channel_sale stock movement per SKU per month. No customer FK — marketplace buyers aren't tracked as retail customers. Excluded from the monthly consolidated e-invoice since the marketplace issues its own. Spec: GAPS.md retail-channel-entry
channel_entries
Engine notes
Shared-data doctrine: ONE customers table (channel enum oem / retail / both) and ONE variant_prices table — data shared, views scoped. What separates Retail from Sell: screens, numbering series (RS- vs SO-), CRM shape (book vs pipeline), e-invoicing path (consolidated vs per-order).
Retail sale posts a retail_sale stock movement (FEFO batch pick) — same ledger, so FG stock and batch trace stay truthful.
Month-end consolidation: one summary document per month per entity → single consolidated B2C e-invoice in QBO/MyInvois (LHDN-permitted). Gaia never talks to MyInvois directly; QBO stays the accounting system.
Floor enforcement in retail is a soft floor: below-floor lines complete immediately and notify the owner (see Retail > Price lists). OEM sales in Sell keep the hard lock.
Channel entries (Shopee etc.): monthly, per-SKU, one consolidated qty + one revenue figure — NOT itemized sales, NO customer records. Posts channel_sale stock movements only, kept out of the B2C consolidation batch since the marketplace already issues its own e-invoice.