Build Report · Confidential
The site is live on its own domain, the backend it needs is running, and the fit assistant works. Below is everything that was built, everything half-built, and everything still open — with the link to check each claim yourself.
Every link below was tested from outside our network before this was sent.
The made-to-measure studio. Pick Custom to see the measurement form and the fit assistant.
odissy.getmaxsolutions.com/made-to-measureWhere products, orders and vendors are managed. Login was sent separately — it is not printed on this page.
api.store.getmaxsolutions.com/appThe backend everything runs on. This link returns a plain health check — that it answers at all is the point.
api.store.getmaxsolutions.com/healthThis is the one genuinely new thing in this build, so it is worth a paragraph.
A custom-stitch order needs eighteen body measurements. Most people do not own a tape measure, so they abandon the form. That drop-off — not the checkout — is what kills made-to-measure online.
Now a customer answers four things they already know: height, weight, the size they usually buy, and a word about their build. The rest is filled in for them as a starting point they correct, rather than eighteen blanks they have to author.
It is written to be honest. It says estimate, never "your measurements". The five that change the cut most come back marked "check this with a tape". If it is ever unavailable the ordinary form still works, so nothing depends on it.
It runs on hardware we already own, so there is no per-use cost. That matters if this becomes a product rather than one site.
5′4″, 62kg, size M → bust 38, waist 30, hip 40, kurta length 48. 5′6″, 58kg, size S, tall → bust 36, waist 28, dress length 42. 5′2″, 70kg, size L, curvy → bust 40, waist 32, hip 42.
Proportions move correctly with the inputs and stay internally consistent.Each of these was verified with a real request, not assumed.
Moved onto getmaxsolutions.com with its own certificate.
This was the thing blocking everything else since 12 July. Saved measurements, cart, accounts and the admin all depend on it existing.
api.store.getmaxsolutions.com/health → 200Products, orders, vendors and the commission settings, in a real interface.
/app → 200 · sign-in verifiedBrowser → site → backend → our own hardware → measurements back into the form.
Full round trip returns measurements · cross-origin check 204Fabric, colours, delivery, wash care; standard sizes with a size guide or custom; eighteen fields in three groups; inches and centimetres toggle; a how-to-measure panel per field; stitching preferences and notes.
Values always stored in inches, converted only for display, so switching units cannot corrupt an entry.Every measurement in both units on one page, generated from the order.
Print stylesheet — no plugin, nothing to install.The main branch carried no routing at all. The whole measurement module existed only on a side branch. The next routine deploy would have published a site with no made-to-measure page and no error to explain it.
Merged and verified: routing present on the main branch.The code that splits an order between the seller and us was writing the wrong kind of value into the ledger, so the build failed on it every time. Nobody had seen it because the backend had never been started.
Build now completes; the corrected code is in the running version.A toolchain mismatch reported itself as a missing file that was sitting right there, which is what made hosting look like a hard problem for three weeks. It was not.
Cause and reasoning written into the setup script so it cannot cost anyone that time again.The shop rejects calls missing an identifying key, and answers with a code that looks like a bad form rather than a missing key. Caught by testing the failure case instead of trusting our own code.
With key 200, without it 400. Fixed before launch.The original password had been committed into the code history. It was replaced before the admin panel became reachable from the internet.
New password accepted, old one rejected — both confirmed.Both the site and the backend now sit on the domain we are standardising on.
DNS, certificates and cross-origin rules all reissued and checked.The address of the backend was only present on one laptop. Any rebuild elsewhere would have published a working-looking page with a dead assistant.
Now stored on the hosting account itself.Started or specified, not finished. Named plainly rather than counted as done.
Product page, sizes, the measurement form, the guidance, the stitching options and the tailor's sheet are done. Saved profiles, cart and the admin split are not.
Needs customer accounts. The backend to store them now exists — it did not this morning — but the accounts themselves are not built.
The eight stages, from Measurements Received through to Delivered, are designed and shown in the interface. No message is actually sent to a customer yet.
The shop can hold ordinary products today. Keeping the two streams visually and operationally separate has not been built.
The product shown is sample data. Real photographs, names, fabrics and prices are needed before this can be shown to a customer.
Nothing here is hidden behind a percentage.
An order carrying eighteen measurements through to payment does not exist yet.
No payment gateway is connected. Nothing can be bought.
It compiles and it is wired in, but no order has ever been placed, so no split has ever been recorded. One real test order is the only thing that proves the commercial model works. This is the single most important open item.
Required before saved profiles or order history are possible.
No courier is connected.
Two directions were recorded at different times. The one now running is the one with a working commission engine. It needs confirming so nobody builds the other.
They change what gets built next, so they are worth more than another week of code.
The mockup the brand colours were taken from has never reached us. The palette in use was sampled from a screenshot.
Answering even two of these is worth more right now than more code.
The written brief listed an AI fit feature as a later phase, not to be built now. It was built anyway, because the project was since described as an experiment to turn this into a product, and this is the part that makes it worth being one.
Saying so rather than shipping it quietly. If it should come out, it comes out — it is self-contained and removing it changes nothing else.