Skip to content

CUSTOM PROCUREMENT SOFTWARE

Bring purchasing, vendors, and locationsinto one workflow.

When requests, supplier records, and payment handoffs live in separate tools, it is hard to see the whole process. Start with the workflow you need to connect, then define the right system around it.

  • Procurement workflows
  • Vendor management
  • Multi-location operations

WHERE THE PROCESS BREAKS

Make the handoffs visible.

For a purchasing team or a business with multiple locations, the important question is where work gets lost between people and systems.

Requests from different locations

Define how a request is submitted, routed, and reviewed for each location.

Vendor information spread across tools

Identify which supplier records and categories need a shared source of information.

Manual checks between teams

Map the handoffs between operations, purchasing, accounting, and treasury.

SCOPE THE RIGHT MODULE

Build around your rules and existing systems.

These are requirements to assess with your team, rather than a claim that every module is needed or included.

Discuss the right scope
01

Purchase requests and orders

Define required fields, location and owner, and when an approved purchase request becomes a purchase order.

02

Vendor records

Define the vendor information, categories, and location relationships the workflow needs.

03

Approvals and exceptions

Set approval roles by location and amount, delegation, rejection rules, and changes requiring reapproval.

04

Purchasing handoffs

Decide what information moves into purchasing and which tool holds each record.

05

Accounting and payment coordination

Define how approved information reaches the people and systems responsible for payment.

06

Roles and process visibility

Agree on access, status information, and the records needed to follow a request.

CLIENT PERSPECTIVES & SELECTED WORK

The Chizy Chiz workflow.

CUSTOM PROCUREMENT · MEXICO

Chizy Chiz

One workflow across a restaurant chain.

Claudia Lugo describes custom software connecting vendor onboarding, location-based categorization, requests, procurement, and the process through vendor payment for Chizy Chiz, a pizza restaurant chain in Mexico.

“It felt as if they had sat down beside me to understand what we experience in our process.”

Claudia Lugo · Chizy Chiz
Explore the client story

Claudia describes the purchasing and vendor workflow for Chizy Chiz in Mexico. The roughly two days she mentions refer to the initial draft; the project then expanded by modules. Watch her account of the work and collaboration.

Watch on YouTube

THE DEVELOPMENT CONVERSATION

Start with one connected process.

A first module can make the project easier to review while keeping the broader process in view.

  1. 01

    Trace a real request

    Follow a recent purchase from its origin through each approval and payment handoff.

  2. 02

    Agree on rules and data

    Document the vendor records, user roles, and systems the module needs.

  3. 03

    Build the scoped workflow

    Review the screens and handoffs against real scenarios from your operations.

  4. 04

    Review before expanding

    Assess the first module and decide which locations or additional workflows to address next.

More about working with Olimpo

BEFORE YOU BUILD

Good questions make a better starting point.

Clarify the scope, responsibilities, and decisions that matter to your project.

Should we build custom software or configure an existing tool?

Test an existing purchasing tool against different approval rules at two locations, an unavailable approver, and an order changed after approval. If configuration meets your rules and integration needs, use it. Assess custom development where material gaps remain.

Can we start with one location or one module?

A location or module can be the starting point if it includes a complete, useful workflow. Agree which supplier records and open purchases move into it, who validates them, and how transactions still in the old process will be completed. Test representative requests and exceptions before deciding to expand, and define a fallback if the agreed checks fail.

Does this replace our POS or accounting software?

Only if that is an explicit part of the agreed project. A procurement workflow may instead connect to existing tools or organize the handoff between them.

Which integrations can be included?

For each connection, identify which system owns each record, what information must move, and who can authorize access. Review available APIs and permissions, and identify any manual handoffs that remain. Keep tracking a payment separate from actually making one. Agree which actions are in scope before estimating.

What does the Chizy Chiz example demonstrate?

The client describes custom software for vendor onboarding and categorization by location, requests, procurement, and the process through vendor payment. It is a documented customer workflow, rather than a promise that every business needs the same system.

YOUR NEXT STEP

Where does your purchasing process slow down?

Start with a high-level example of a recent purchase: the locations and people involved, where vendor records live, and the handoff you want to improve. Describe the process without sharing confidential vendor, financial, or customer records.

Map Your Procurement Workflow
  1. 01Which locations and teams are involved?
  2. 02Where do vendor and purchase records live?
  3. 03What should the first module connect?