Packaging pricing is the kind of arithmetic that ruins afternoons: dimensions, board grades, quantities, finishes, each variable feeding the next. Before this exhibit entered service, that arithmetic lived in heads and spreadsheets. Now it lives at quote.pakko.com.au, and the desk can report it does not make transcription errors.
The construction is familiar to readers of this file: a Next.js front-end over a Supabase core. But examination turned up something the other exhibits don't have — a MySQL slice holding part of the pricing data, kept alongside the Supabase layer, with AWS handling the assets. Two databases at one scene is usually a sign of history; the subject wired them into a single engine rather than pretending the history away.
The engine sits at the centre of the pipeline this paper has documented across three exhibits. Specs arrive from the storefront (Exhibit B) or the 3D design platform (Exhibit D); priced orders leave. What passes through the middle is this machine's business.
“Two databases at one scene is usually a sign of history. He wired them into a single engine.”
The engine remains in production, pricing orders as they arrive. The investigation finds the subject comfortable in the unfashionable middle of the stack — where the money arithmetic lives — and considers that the strongest evidence in this exhibit.