Customer workflow planning
Manufacturing Customer Portals
A manufacturing customer portal can connect customer order queries, change requests and approved documents to a controlled review process. Keep requested changes separate from accepted production instructions and make the current version clear.
Focus on the customer-to-production handover
When an order change arrives by email while a different drawing is already in use, the issue is not simply document storage. The business needs a dependable way to decide what changed, whether it is accepted and which instruction remains current.
A customer portal is a candidate when these exchanges recur and someone owns order review. It is not a substitute for production planning, engineering judgement or a quality-management process. Start with an order query or change request that can be completed without granting customers direct control over production.
This is distinct from customer reporting: the focus is a reviewed change and its accepted outcome, not just presenting figures. The portal service page explains the wider delivery context.
Separate a request from a released instruction
A customer should see that their requested change was received without being led to believe it has been accepted. Capture the order reference, affected item, proposed change and relevant evidence. Route the request to the people responsible for feasibility, commercial impact and scheduling.
- Requested: captured for review, with no production commitment.
- Under review: an accountable person is resolving the decision.
- Accepted or rejected: the decision and any conditions are recorded.
- Released: the responsible team has confirmed the applicable instruction in the operational process.
These are illustrative states to adapt with the operator. Do not introduce a state that the underlying process cannot reliably confirm.
Make the accepted revision unambiguous
Connect each document to the relevant order or item, preserve its identifier and display its review state. A newest upload is not necessarily an approved revision. Prevent an old approval from silently applying to changed content.
Hypothetical example: a customer uploads a revised specification for an open order. The portal records a change request and retains the existing accepted specification. The responsible team reviews the proposed change and confirms the replacement only after the required decisions are complete.
Define how superseded documents appear and who can retrieve historical versions. Use the document management guide and approval workflow page for supporting controls. The portal must not imply engineering certification or product conformity merely because a document was uploaded or clicked.
Keep production authority in the right system
Identify where order status and released instructions are maintained. Decide whether the portal only reads selected milestones or submits a request for an internal team to process. Confirm available interfaces and approvals with the ERP or production-system owner.
Show source timestamps and distinguish planned milestones from confirmed events. Handle a delayed integration as an uncertain update, not an instruction to repeat a production action. Preserve request identifiers so retries can be detected and reconciled.
The integration guide covers contract and recovery questions. Avoid promising an existing-system connection before its access and operations have been verified.
Test the boundary before expanding
Restrict customer access to authorised orders, files and actions. OWASP recommends checking permissions on every request; hiding a link does not provide that boundary.
Pilot one order category. Test a revised file after approval, a rejected change, an inaccessible order, a duplicate request and an unavailable source system. Confirm that staff can identify the applicable instruction without reading several competing messages.
Measure unresolved change age, clarification effort and requests completed with a recorded decision. These are proposed measures, not established performance claims. Agree necessary quality, safety and specialist reviews with the operator, then estimate the smallest useful release with the development team.
Sources and review date
Sources reviewed on 8 September 2026 are linked beside the guidance they support. Workflow designs and measures are planning recommendations, not measured client results. Examples are hypothetical. Confirm scope, integration access and any specialist-review requirements with the responsible team before implementation.
Questions
Frequently asked questions
Can customers change production orders directly?
That should not be assumed. A first release can capture requests for authorised review while production changes remain controlled by the responsible team.
Is the most recent uploaded file the approved version?
Not necessarily. Store version and approval state separately, and identify the instruction currently accepted by the responsible team.
Plan your next step
Bring the workflow you want to improve.
Discuss the current process, systems and first useful release with LCR Technologies.