Order Flow Process

Sign in

Every page now sits behind a 4-digit PIN. shared/header.js redirects unauthenticated browsers to /login.html; signed-in users get their role's home page (admin → /, sales → Sales Station, cutting → Material Cutting Station, stock → Warehouse Station). Roles restrict which pages a user can navigate to — the allow-list lives in ROLE_PAGES.

Actor name on every audit event (stock_in/out, order_log, serial allocations) is the signed-in user — the legacy x-sarkar-employee header is overwritten server-side so a rogue client can't spoof identity.

Stored in: auth_users (name + PIN hash + role), signed HttpOnly cookie whose secret lives in auth_meta (survives restart).

Customer & Enquiry

Customer profile is created or selected. Address, payment terms, currency, Incoterms and tax ID are stored. This feeds directly into the CIPL generator (Step 9) — consignee + bill-to auto-fill from the customer.

If the order ships to our Plano warehouse (default for any P-prefix job), the Sarkar Tactical Inc. (Plano) contact — Sanjay Sood, 542 Haggard St — is already in the customers + suppliers list.

Create Order

A new order is created as a draft. Client name, delivery date, currency, Incoterms, payment terms, export licence. No job ref burnt yet.

Export compliance: new Licence number field (ECJU SIEL / OGL) flows onto the CIPL in Step 9. Ship to Plano checkbox auto-ticks for P-prefix job refs — when on, CIPL swaps the consignee to our Plano warehouse address automatically.

Add line items from the catalogue — each line has item, size, colour, quantity, unit price. The catalogue cascading dropdowns prioritise items with stock, and Quick-add item has Category → Subcategory → Item filtering plus a currency picker (£ / $ / €) for the unit price. The SKU-reuse check uses (category, item, size, colour, variant) — the DB unique key — so you don't hit "already exists" errors when typing a new manufacturer.

Line-item qty edits no longer lose focus (the inner table rebuild was fixed); size / colour dropdowns are datalists so you can pick existing values or type anything new (3X-Large, 4XL, any custom colour) — order lines import into the carrier / ballistic job sheets even when the exact variant isn't in the catalogue.

When ready, Save & allocate job ref → picks G (Glasgow) or P (Plano) series → draft becomes an open order with a permanent job ref like G26-029.

Item library prep (one-time per SKU)

Before an order can generate sheets automatically, each item involved must have complete data. Every missing field below shows up on the Data Audit page.

Generate job sheets from the order

On the order page, the Attached job sheets & documents card has "+" buttons that launch each sheet generator pre-filled (?orderId=N), plus a + Upload file button for PDFs / Word / Excel / images (up to 30 MB). Every sheet can be Sent to Order so the snapshot lives under the order file.

Every sheet has a Preview & download dialog — a modal that mirrors the PDF layout so you can eyeball the finished job + edit any free-text blocks (notes, materials, patterns, composition) before committing to the PDF. Consistent across Carrier, Helmet, Ballistic, and CIPL.

Allocate serials

Generate Serial Numbers on the order page runs through every order line and maps the item category to a pool code. Lines can be drag-reordered on the order page — drop to renumber from 001 in the new sequence. The refresh semantic purges every serial matching jobRef.* (not just order-linked ones) so orphans left by manual allocations don't shift counts.

Inputs: order id, job ref, line items, pool code per item category (or a per-catalogue-item serial_pool_code override for things like detectors / cable reels / EOD kits).
Calculation: next unused sequence for the (pool, jobRef, yyww) prefix, or a user-typed prefix override for back-filling historical orders.
Custom serials: on the Labels page you can + Add custom serial with any string — useful for back-filling legacy or one-off re-prints.
Manage types: ⚙️ Manage types dialog on /serials.html adds, renames, or archives pool codes (HEL / CAR / SAP / HAP / DET / EOD / …). Codes are immutable once created (already-allocated serials embed them).
Outputs: serials like G26-029.2616-CAR-001 for CAR, HEL (×1 label), SAP (×3 labels — front/back/spare), HAP (×1 label). Printable label sheet PDF.
Saved to: serial_allocations (linked to order_id, with optional label_category_override for the labels grid). Event logged to order_log as serials_allocated.

Label print tracking

Dense orders × label-kinds grid: rows are orders, columns split into SEW ON ribbon (CAR Paper) and STICK ON ribbon → BIG Labels (HAP, BIG SAP) + SMALL Labels (HEL, HEL w/ Visor, SMALL SAP). Auto-classifier routes allocations to the right cell from pool code + assigned-to keywords; per-allocation label_category_override lets operators reclassify.

Per-cell: serial range + total labels (factoring label_repetition), a top-right tick to toggle printed (turns green) without opening a dialog, and a click-through detail popup where you can edit category / assigned-to / repetition, delete serials, or add custom serials. Notes field records "ribbon smudged, re-print" etc.

Top-bar buttons: ✓ ALL PRINTED marks every visible cell printed (respects active filters), 📄 PDF — Print queue exports unprinted cells, 📄 PDF — Printed log exports printed cells (records / archive).
Stored in: order_label_prints (order_id × category → printed, notes, updated_by).

Procurement execution

The Order Sheet from Step 4 tells you exactly which suppliers to contact and what quantities to request. One PDF per supplier.

Inputs: Order Sheet's procurement rows (from order_attachments).
Stored: supplier profiles in suppliers — contact details, MOQ, payment terms, category tags.
When stock arrives: log via Warehouse Station (/warehouse-station.html) or Material Cutting Station. Writes to stock_in (for items) or material_deliveries (for fabrics). v_dashboard re-aggregates live.

Production + material usage

The cutting / sewing / assembly teams work from the PDFs generated in Step 4. Materials get drawn from stock as production progresses.

Inputs: Ballistic Job Sheet PDF (for cutting room) + Carrier Job Sheet PDF (for sewing) + Helmet Job Sheet PDF (for assembly) + Serial labels.
Stock out events:

• Factory floor logs cuts in Material Cutting Station → writes material_usage rows (per-size breakdown), deducts from materials.stock_on_hand.
• Warehouse logs dispatch of FG parts via Warehouse Station → writes stock_out.

Every action against the order (attachment added, serials allocated, status change) appends a row to order_log and surfaces in the Order log card on the order page.

Quality & Packing (future)

Hooks are in place; dedicated pages still to build.

• Stock check list per order — compare order lines vs v_dashboard stock on hand. Warehouse ticks off each item.
• Finished goods check list — every serial from serial_allocations checked against physical labels.
• Net weight per item — already stored in catalogue.net_weight, feeds packing declarations.

Commercial documents & dispatch

Commercial Invoice + Packing List is now live as a single two-page PDF — see Step 4's CIPL sub-item. Everything auto-fills from the order header + order_items + catalogue hydration, so a typical shipment is: pick order → preview → download. Shipments through the Plano warehouse get Sanjay's address on the consignee block automatically from the Ship-to-Plano flag.

Still manual: box allocation (pcs/ctn, net/gross weights, dimensions) — the CIPL seeds one carton per line item and the operator fills in actual weights as boxes get packed.

Order status moves: draft → open → in_production → shipped → closed. Every status change is logged in order_log.

Year-end tally: the Shipped Orders page (/completed.html) rolls live shipped orders + legacy CSV imports into a per-category / per-item tally. Grouping toggles, category filter, CSV export, year picker.