Different roles, different visibility.
Buying needs supplier information to assess and negotiate an offer. Sales needs the approved product and selling terms to prepare a customer offer. Those responsibilities do not require identical access.
The underlying application enforces role restrictions server-side. Supplier identity is restricted for Sales; internal cost and margin fields are also restricted on the relevant Sales workflows. This is more than hiding a column on screen.
We agree the role and field policy for each implementation, including original-file access and downloaded workbooks. The exact coverage is checked against the screens, routes and outputs in scope before handover.
Keep the source available for review.
Structured records should remain connected to the material received. Authorised users can open original supplier files and inspect source issues when a product, price or commercial field needs checking.
Missing prices and uncertain fields need an explicit review. A comparison should make clear what came from the supplier, what was normalised and what remains unresolved. Source references help the operator investigate the result and check a correction against the original.
Human approval controls the handoff.
Recommended actions help Buying decide where to focus. Buying reviews the relevant list and approves the selling terms before Sales prepares its customer-facing output. Matching supply to a request does not place an order, confirm a sale or send a customer message.
The approval scope, permitted prices and output fields need to be explicit. A customer workbook is checked against those rules as well as the screen used to prepare it.
Agree the connected workflow before implementation.
The pilot defines supported inboxes and files, extracted fields, product matching, commercial rules, roles, outputs and acceptance checks. Connections to systems such as Odoo are scoped to the customer's setup, including read access, any proposed writes and the approval required.
Hosting, data handling, retention, recovery and service expectations belong in the written implementation and operating scope. We confirm those requirements for the chosen setup before delivery.
Discuss your requirements with us.
Bring the workflow and access requirements to a guided walkthrough. We can then agree the route for representative material and the controls to validate in a paid pilot. Please do not put confidential files or credentials in the booking form.
For product or implementation questions, contact hello@pycache.com.