Questions, answered

Click Get started, then use Proto to configure ERP for Pharma for your business. Start with a reviewed product definition, an incoming supplier lot and a production order. Follow accepted output through batch review and a stability pull, then reconcile its stock and financial effects before expanding.

The Batch Release Reviews screen presents a batch release review queue, status distribution, certificate and expiry evidence, and selected-record review history. The batch release review links the review to lots and quality reviewer in the person record. Confirm the reviewer account mapping and controlled decision route during setup.

The batch review status records the specialty decision. The quality hold retains its own disposition and release attribution. Rehearse the operating controls that connect eligible production and shipment to required quality decisions; review both decisions before treating the material as usable.

Each stability study records batch, storage condition, pull date, result and disposition. Pending, Accept and Investigate separate the evidence states. Configure the correction route to retain original evidence and attributed successors, then reject repeated capture of the same source evidence.

Separate evidence preparation from the human decision. Agree the permitted approval route with Industry Reviewer and Approver, then rehearse it using their actual accounts. The preparer must be refused if they attempt to approve their own purchasing commitment.

Each lot carries expiry date and status. Require lot-controlled issue to use an Available, unexpired lot of the intended product. Rehearse the expiry boundary and unresolved holds against actual movement commands before relying on the control.

Use the lab’s approved result records and the controlled-document system agreed with your quality owner. Map each result to the correct batch, retain its actual evidence date and review corrections against the original. Agree provider access and the acceptance checks before enabling the connection.

Connections require explicit configuration, provider access and source mappings. Agree the source owner and permitted operating command for each feed. Rehearse duplicate events, wrong references and external failures before enabling a feed; see integrations.

Bind each receipt, completion, shipment and material posting to its actual source identity so retries return the original effect. Test repeated commands and conflicting content during implementation. Batch review and stability capture must not create another physical or financial effect.

Use the pricing page for the published policy. Agree implementation scope after reviewing your reference mappings, approval routes and required connections. The implementation plan sets out the pilot evidence to review before wider cutover.