FAQs for every Procuraz participant.

It is designed for organizations that want a more structured procurement process, employees who raise purchase needs, approvers and finance users, suppliers that participate in sourcing and orders, and authorized Procuraz seller partners.

Yes. Users access the appropriate Procuraz portal through a web browser. The available functions and data depend on the organization, role, subscription and product configuration.

Procuraz is focused on procurement workflows. It may complement an ERP, accounting or inventory system. Any integration or data-exchange capability should be confirmed for the applicable deployment rather than assumed.

The product model includes requisitions, approvals, vendor management and onboarding, RFQs, quotation comparison, supplier selection, purchase orders, receipt and material acceptance, catalogs, user administration and operational reporting.

No. Website previews use illustrative demonstration names, values and transactions to explain how the interface works. They are not records from a customer account.

Procuraz is designed for an instant-implementation approach in which a company can create its cloud workspace and begin configuring users, departments and vendors without a traditional infrastructure project. The actual setup effort depends on the company’s policies and data readiness.

Use the contact form or email the relevant team: sales at sales@procuraz.com, support at support@procuraz.com, vendor help at vendors@procuraz.com, technical support at tech@procuraz.com, or partner support at partners@procuraz.com.

Company administrators, procurement users, employees, approvers, finance users and management users sign in through https://app.procuraz.com.

A company can begin through the Start Now or Start Trial buttons. Registration, subscription selection and any verification steps are completed in the company application.

Yes. Department capacity depends on the selected plan. Departments provide organizational context for users, purchase requests, approvals and reporting.

Yes. Authorized company administrators can create or invite employees within the user capacity of the subscription. Each user should receive an individual account rather than sharing credentials.

Yes. Procuraz is designed around role-based access. The exact permission set depends on the role and product configuration assigned by the company administrator.

Yes. The product model supports multi-stage approval routing. A company can structure authority around roles, departments, reporting responsibility and value thresholds as supported by its configuration.

Authorized company users can create vendor records for suppliers already known to the company and maintain the profile and documentation required for internal procurement use.

The company creates an onboarding invitation and sends the link to the prospective vendor. The vendor completes the form and uploads required records. The company can approve, reject or request changes. Once approved, the supplier can be added to the company vendor master.

Yes. The onboarding process can distinguish required and optional documents. Typical records include GST registration, PAN, bank proof or cancelled cheque, registration records and authorized-signatory documents.

A permitted reviewer can inspect the submitted information and documents, approve the onboarding, reject it with a reason, or return selected details for correction and resubmission.

Yes. Procurement users can create a sourcing event from an approved requirement and invite suitable vendors to respond within the specified window.

Yes. Procuraz is designed to present supplier responses in a structured comparison that can include value, taxes, delivery, payment terms, warranty, compliance and evaluation notes.

Yes. The approved sourcing or buying decision can be converted into a purchase order so the supplier, line items, value, terms and records remain connected.

Yes. Receiving users can record delivered quantity against the purchase-order line items and capture acceptance, rejection or inspection status.

Dashboards and reports are intended to provide role-appropriate visibility over demand, approvals, sourcing, suppliers, purchase orders and exceptions. Exact reports may vary by product release and permissions.

The employee opens the company application, creates a purchase requisition and enters the requested items or services, quantity, estimate, required date, department, justification and supporting documents.

The workflow is designed to support draft preparation before submission. Availability can depend on the current product release and the permissions assigned to the user.

The approval route is determined by the company’s configured authority. The requester can follow the current stage and status without needing to manually forward the request.

The request is sent back for correction with the recorded reason or comments. The responsible user can amend the information and resubmit it through the workflow.

Approvers should receive the business context available for their decision, including line items, value, justification, department and supporting records permitted by their role.

The system should restrict approval actions to the authority and role assigned by the company. A user must not attempt to bypass access controls or use another person’s account.

The requester can follow the status made available by the company’s permissions and product workflow, such as approved, sourcing, ordered or completed.

Report a reproducible technical problem through the contact form with “Technical issue” selected or email tech@procuraz.com. Include the page, time, steps and error message without sending passwords or secret keys.

Vendors and suppliers use https://vendor.procuraz.com. They should not use the company application or seller-partner portal for supplier activity.

Fresh vendor onboarding is normally initiated by a company invitation. Follow the link and instructions provided by the buying organization. General vendor questions can be sent to vendors@procuraz.com.

A company may request legal name, constitution, addresses, tax registrations, PAN, bank details, contacts, categories, authorized signatory information and other supplier-compliance information relevant to its policy.

The exact list is set by the inviting company. Common examples include a GST certificate, PAN card, cancelled cheque or bank proof, certificate of incorporation or registration, MSME/Udyam record where relevant, and authorized-signatory identification or authority documents.

A required document must be provided before submission can be completed. An optional document can be supplied when applicable but should not prevent submission if the company has marked it optional.

A change request means one or more fields or documents need correction, clarification or replacement. Review the comments, update the indicated items and resubmit for company review.

The supplier becomes approved for the company after an authorized company reviewer accepts the onboarding. Submission alone does not guarantee approval or business allocation.

Yes, when invited by a company and permitted by the current workflow. Vendor users can review requirements and submit commercial responses and supporting records before the deadline.

The vendor workspace includes catalog-management concepts, including structured records and bulk upload. Availability and company visibility depend on the current release and permissions.

The catalog bulk-upload section is intended to provide a sample template aligned to the catalog fields. Complete the template without changing required column headers, then upload it for validation.

Relevant vendor users can access purchase-order activity made available by the buying company and the current product configuration.

No. Vendor users can provide information and respond to company requests, but company approval, sourcing and purchasing decisions remain under the buying organization’s control.

Use the website form and select Vendor or supplier support, or email vendors@procuraz.com. For a technical error, you may also copy tech@procuraz.com.

Authorized seller partners use https://partner.procuraz.com.

No. A vendor supplies goods or services to a buying company. A seller partner participates in the Procuraz channel or commercial ecosystem under a partner relationship.

Use the contact form and select Seller partnership, or email partners@procuraz.com. Approval and commercial terms are governed by the applicable partner process and agreement.

The partner workspace is designed to support authorized partner teams. User and role capabilities depend on the current Seller Partner Central release and the partner agreement.

Only data and functions expressly made available within the partner scope should be accessible. Partner status does not grant unrestricted access to a customer company workspace or its procurement records.

No. Seller partners should use partner.procuraz.com. The vendor portal is reserved for supplier relationships with buying companies.

Partner programme and workspace enquiries should be sent to partners@procuraz.com. Technical errors can be reported to tech@procuraz.com.

The Trial plan lasts 30 days, costs ₹0 and includes 5 users, 5 departments, 10 vendors and 1 GB of storage.

Starter is an annual plan priced at ₹11,999 and includes 2 users, 2 departments, 5 vendors and 2 GB of storage.

Growth is an annual plan priced at ₹24,999 and includes 5 users, 5 departments, 25 vendors and 5 GB of storage.

Professional is an annual plan priced at ₹74,999 and includes 50 users, 20 departments, 150 vendors and 25 GB of storage.

Advanced is an annual plan priced at ₹1,24,999 and includes 200 users, 100 departments, 500 vendors and 50 GB of storage.

Starter, Growth, Professional and Advanced are annual subscription prices. Trial is a 30-day, zero-cost plan.

Applicable GST or other taxes may be added according to law, the invoice, checkout process or Order Form.

The company may be unable to add more users, departments, vendors or storage beyond its subscribed capacity until records are removed where appropriate or the subscription is upgraded.

Upgrade options and commercial adjustments should be confirmed in the application or with sales@procuraz.com.

A downgrade may be subject to the renewal date, current usage and the applicable Order Form. The company may need to reduce users, departments, vendors or stored data to the lower plan limit before the downgrade takes effect.

Access may be limited or suspended until the company selects a paid plan. The Trial does not guarantee continued access after 30 days.

Unless required by law or stated in the Order Form, annual subscription fees are generally non-refundable after activation. Cancellation normally stops future renewal rather than reversing the current paid term.

As between Procuraz and the customer company, the customer retains its rights in the data it submits or controls, subject to the licence required for Procuraz to host, process, secure and provide the service.

The product architecture is intended to logically separate company, vendor, partner and platform-owner workspaces. Access must still be configured correctly by administrators and verified in production.

Passwords should be processed using secure one-way hashing and must never be sent by email or shared between users. Users are responsible for maintaining strong credentials and protecting access to their mailbox and devices.

Yes. The product model uses roles and organization scope to determine permitted data and actions. Customers are responsible for assigning appropriate roles and removing access when it is no longer required.

Production Procuraz websites and applications should be accessed over HTTPS/TLS. Users should verify the correct procuraz.com domain and avoid continuing through browser security warnings.

No certification should be inferred unless Procuraz publishes a current, verifiable statement or provides it in a signed contract. The public Security page describes the intended control framework without inventing certifications.

Email tech@procuraz.com with a clear description, affected URL, steps to reproduce and evidence that does not expose unnecessary personal data. Do not publicly disclose the issue before Procuraz has had a reasonable opportunity to investigate.

Contact support@procuraz.com and identify the account or organization involved. When Procuraz processes data on behalf of a customer company, the request may need to be handled by that company as the relevant data fiduciary or controller.

The public website is designed to operate with essential browser functions and does not require advertising cookies. If non-essential analytics or marketing technologies are introduced, the Privacy Policy and consent mechanism should be updated before activation.

Use a currently supported version of Chrome, Edge, Safari or Firefox with JavaScript and cookies enabled where required for authenticated application functions.

Include the portal URL, date and time, your role, the page or record involved, exact steps, the visible error and a screenshot with sensitive data removed. Never send passwords, private keys, OTPs or full payment details.

Sales, demos, plan selection and commercial questions are routed to sales@procuraz.com.

General support and account enquiries are routed to support@procuraz.com.

Vendor onboarding and supplier portal questions are routed to vendors@procuraz.com.

Seller-partner programme and workspace enquiries are routed to partners@procuraz.com.