Product documentation / WexaProcure

WexaProcure Scope & Evaluation Guide

Review WexaProcure: Purchase requests, budgets, approvals, supplier quotations, orders and receipt follow-up. Confirm the current evaluation boundary, tasks and remaining delivery requirements.

Scope and versionLocally qualified V9 customer-administration scope, reviewed 16 October 2026. V9 identifies a development scope, not a public semantic release or customer activation.

What the product does.

WexaProcure connects internal purchasing requests with budgets, approvals, supplier quotations, orders, delivery acceptance and contract follow-up. The current source package has local qualification evidence.

Locally qualified source package. Customer acceptance, live ERP effects and production deployment remain separate.

Product capabilities

Give purchasing a traceable path

Connect requests to budget review, approvals, supplier RFQs, quote scoring, orders and delivery acceptance. Supplier selection and independent approval remain distinct decisions.

  • Purchase requests, budgets and approvals
  • Supplier RFQs and quotation comparison
  • Orders, receipts and contract follow-up

Work across companies and locations

Company and site permissions bound what each actor can see and do. The local scope includes supplier access, delivery follow-up and customer administration, with English as the default and Turkish support.

  • Company and site access scopes
  • Supplier intake and delivery follow-up
  • English and Turkish workflows

Evaluate the relevant tasks.

Use these tasks to prepare a demo. Confirm the supported behaviour for your version and operating environment.

  1. Choose a sample request, company, location and budget owner.
  2. Compare supplier quotations and review the separate approval decisions.
  3. Follow an order through delivery and receipt exceptions.
  4. Agree ERP ownership, financial effects and customer-installation acceptance.
Arrange a product demo

Workflow walkthroughs

Review a purchase request through receipt

Describe your request, approval and supplier process, organization structure and target ERP. Keep real supplier documents and prices out of the general enquiry.

  1. Choose a sample request, company, location and budget owner.
  2. Compare supplier quotations and review the separate approval decisions.
  3. Follow an order through delivery and receipt exceptions.
  4. Agree ERP ownership, financial effects and customer-installation acceptance.

Prepare a useful support request.

Include the exact WexaProcure package or preview, environment and workflow. Confirm whether the issue concerns a local evaluation or an accepted customer installation.

  • Describe your request, approval and supplier process, organization structure and target ERP. Keep real supplier documents and prices out of the general enquiry.
  • Describe expected behaviour, what happened and any steps already tried. Do not send passwords, tokens, private files or production records.
  • Remaining acceptance scope: Customer installation and operational acceptance; Real ERP stock and financial effects; Production deployment and external service activation.
Get product support

Your questions, answered.

Does local qualification mean our ERP is already connected?

No. Real ERP stock and financial effects require their own approved integration and acceptance.

Can purchasing permissions differ by site?

Company and site scopes are part of the product model. Your organization, roles and approval responsibilities are reviewed during evaluation.

References and product context