One record per customer enquiry, one ID that follows the box, and a stage everyone can see.
A customer enquiry for packaging moved between Sales, Design, Graphics and Commercial by email, spreadsheet and word of mouth. Nothing followed the job, and a sales rep could not answer 'where is my enquiry' without asking around.
An enquiry workflow built to the way the site works, replacing a generic work-management tool.
Item versus enquiry
A quote mints a new box specification. A sample, artwork, pallet plan or test can only attach to one that already exists.
Deny by default, once
The same scope and permission checks run unchanged on the web and on the phone, because both read the same verified identity.
A deploy that checks itself
Every affected page is fetched after upload. A blank page, a 404 or a fatal fails the deploy and names the page.
Not an ERP. Deliberately.
The site's existing systems stay where they are. Flute sits beside them, signs in through Prolink Hub, and reaches the phone through the same identity.
The enquiry now has one record, one ID that follows the specification, and a stage the whole site can see. Iteration two replaces sign, scan and upload with a secure expiring approval link for the customer.