Versatile 134

Custom Operating Systems
for 3PLs &
Product Driven Brands

We build custom software that connects the requests, records and updates your team still has to piece together across emails, spreadsheets and warehouse systems.

OutlookOutlookNew
CClient servicesSubject

Acme Outfitters | AO 1048


Please use plain packaging
for this order.

One new instruction.
Microsoft ExcelExcel
Acme_order_updates.xlsx
A
B
1
Order
Packaging
2
AO 1048
Branded
3
New request
Plain
4
Confirmed?
Waiting
Which version reached the floor?
SlackSlack

# warehouse ops

CS
Client services

Did the floor see the change
to AO 1048?

WL
Warehouse lead

Checking now. Has picking
already started?

The team keeps the story straight.
Extensiv
Acme OutfittersAO 1048
Awaiting pick
Packaging
Branded
New instruction
Plain requested
Review
Not confirmed
The order is here. The conversation is elsewhere.

Good systems can handle the orders.
People still handle the conversations between them.

Give that work
a place to happen.

Good software.
Still a lot of chasing.

Here’s how a few useful tools can turn into a lot of work keeping them in sync.

  1. A spreadsheet gets you started.

    A few orders, a few products and a small team. A shared sheet is a practical way to keep track. As more people need it, copies spread and someone has to work out which version is right.

  2. Then the specialist tools arrive.

    A WMS gives warehouse work a home. An ERP handles purchasing and finance. Each does an important job, but a client instruction or supplier update can still arrive somewhere else.

  3. The work between them stays manual.

    The order is in one system. The new instruction is in an email. The stock check is in a spreadsheet. Each record makes sense on its own. Your team still has to put the story together.

  4. Your team becomes the connection.

    Someone checks which detail changed, asks the warehouse what happened and updates everyone else. The work gets done because people know who to chase. When that person is away, the rest of the team has to retrace their steps.

  5. AI still needs the right information.

    AI can help read a message or draft a reply. But if the order has changed and the information it sees has not, the answer needs checking. A faster answer is only useful when it reflects what actually happened.

  6. Connect the work. Keep people in control.

    Start by checking what your existing tools can already do. Where a gap remains, bring the request, relevant records, responsible person and response together. People can review the decision, and the next person can see the outcome.

What if the next person
already had the answer?

A custom operating system gives your team a place to review the request, see the relevant records and keep track of what needs to happen next.

See how a packaging
change gets handled.

Here’s how a request for plain packaging could move from client services to the warehouse, with the review and response kept alongside the order.

A new instruction comes in.

Say a client asks for plain packaging after the order is in. The message stays with that order so the warehouse can see exactly what needs to change.

Packaging requestAO 1048
Request received
Order state
Awaiting pick
Packaging
Branded
Owner
Client services

The message is linked to order AO 1048.

Packaging requestAO 1048
Request received
Order state
Picking started
Packaging
Branded
Owner
Client services

Picking has started, so the original instruction is still in place.

Check whether it can still change.

Before anyone changes the instruction, check whether picking has started. If it has, the warehouse supervisor needs to decide whether the change is still possible.

Packaging requestAO 1048
Under review
Order state
Awaiting pick
Packaging
Branded
Owner
Operations reviewer

Operations is checking whether the instruction can still be changed.

Packaging requestAO 1048
Needs a decision
Order state
Picking started
Packaging
Branded
Owner
Warehouse supervisor

The supervisor is checking whether the change can still be made.

Send the approved instruction.

Once the change is approved, the warehouse gets the new instruction. The request stays open until someone confirms what happened.

Packaging requestAO 1048
Awaiting response
Order state
Awaiting pick
Packaging
Plain requested
Owner
Warehouse lead

The request stays open until the warehouse responds.

Packaging requestAO 1048
Awaiting response
Order state
Picking started
Packaging
Branded
Owner
Warehouse supervisor

The order stays unchanged while the supervisor reviews the request.

Client services can confirm the change.

When the warehouse confirms the new instruction, the reply is saved with the request. Client services can then give the client a clear answer without chasing the floor again.

Packaging requestAO 1048
Confirmed
Order state
Awaiting pick
Packaging
Plain
Owner
Warehouse lead

The warehouse confirmed the change to plain packaging.

Packaging requestAO 1048
Response recorded
Order state
Picking started
Packaging
Branded
Owner
Client services

The supervisor declined the change because picking had already started.

AO
Acme OutfittersOperations workspace
CSWL

Orders / AO 1048

Packaging change

Confirmed
Outlook
Client servicesAcme Outfitters

Please use plain packaging
for this order.

Linked to order AO 1048

Activity

  1. Request receivedClient instruction linked to the order
  2. Operations reviewOrder state and permitted action checked
  3. Instruction sentThe warehouse has the approved change
  4. Response recordedThe answer stays with the request

Warehouse record

Extensiv
Response recorded
Order
AO 1048
Order stage
Awaiting pick
Packaging
BrandedPlain
Responsible team
Warehouse lead

Warehouse confirmation received

Client services can confirm the change.

The warehouse confirmed the change to plain packaging. The reply stays with the request so client services can give the client a clear answer.

Built for 3PLs and
Product Driven Brands.

Fulfilling orders for other businesses

3PLs

Your team takes instructions from different clients, gets them to the warehouse and checks what happened. We build systems that keep the request, the action and the response together.

  • Get client changes to the warehouse
  • Keep stock counts and discrepancy checks together
  • Prepare client reports and records of extra work
For 3PLs
Initially focused on your own fulfillment

Product Driven
Brands

When you manage your own fulfillment, a product update or supplier delay can change what happens in the warehouse. We build systems that help your team see what changed and what needs doing next.

  • Keep product and supplier updates in one place
  • Give the team stock information it can check
  • Confirm order changes with the warehouse
For Brands

Sometimes the right build
starts with a setting.

First, check what your current software and vendor can already do. A better setup or a supported connection may close the gap.

When something is still missing, we define the custom part around the records and tools that already work.

Check the existing route

Features, configuration, vendor support and tools you already pay for.

Confirm the connection

Which system owns each record, what can be read or changed, and who approves it.

Build the missing part

A practical interface, the agreed rules and a visible route when something needs attention.

Build on what already works.

The right tools
for the way you work.

We choose the building blocks around your workflow, existing systems and budget. Custom code fills the parts that need a closer fit.

Shared records

Keep the information people need in a usable place.

AirtableSupabase

Connections

Move approved information between the right tools.

Maken8nZapier

Team interfaces

Give people a focused place to review and act.

SoftrBubble

Work out what needs fixing.
Then decide what to build.

A polished demo is easy to like. Living with the wrong system is harder. We follow the real work, check what you already have and agree the first useful change before the build.

Show us where the work gets stuck

Bring one recent example. We follow the request through the messages, spreadsheets and systems with the people who actually handle it.

Your team brings

A process owner, a recent example and the people who know the job.

Work out what needs changing

Check the existing setup before adding to it. A setting, a vendor feature or a clearer process might be enough. If a gap remains, define it.

We agree together

The problem, the systems involved and the first useful scope, with pricing and responsibilities clear before work starts.

Build it. Try the awkward cases.

Review a working version together. Test the normal job, the late change, the missing information and the update that fails. A happy path alone is not a finished system.

Your team reviews

The prototype and test results. A named person accepts the agreed change before it becomes part of daily work.

Hand over something people can run

Show the team how the system works, where to find the record and what to do when something needs attention. Agree who handles support.

You receive

Your custom code and documentation. Maintenance scope and cost are agreed separately.

The people doing the work need a seat at the table.

Your team helps explain the job, checks the proposed change and tests the result. We agree that involvement before anyone commits to a build.

Who this is for.
And who it is not.

A recurring problem is a useful starting point. The right timing and people matter just as much.

This is for you if

  • You run a 3PL fulfilling orders for other businesses, or a Product Driven Brand managing its own fulfillment.
  • The same request, update or report keeps sending people between tools to piece together an answer.
  • Someone can own the process and involve the people who use it.
  • You want to check the options before committing to software or a build.

This is not for you if

  • You only need a standard store setup or a WMS feature your current vendor can already provide.
  • You expect software to settle decisions your team has not agreed.
  • Nobody can review the process, authorize access or test the result.
  • You want changes pushed into live systems without clear rules or review.
Still getting used to a new system?

Bring a specific blockage if there is one. If the setup is still settling in, collect a few examples first. You do not need another system just because the first week was awkward.

People who have
worked on the floor.

We’re Benjamin and Gavin. Our backgrounds are in logistics and manufacturing. That is where our interest in the work behind the screens comes from.

Meet Versatile
Benjamin Orlof
Benjamin OrlofCo founder
Gavin Babel
Gavin BabelCo founder

Before you
commit to a build.

The questions worth sorting out first.

All questions
Do we need to replace our WMS or ERP?

Keeping a system that works is often the sensible choice. We check its features, configuration and vendor support before proposing custom work. If a setting or your existing vendor can fix the problem, that is where we should start. A new interface is only useful if it solves something the current setup cannot.

Should we buy a WMS, ERP, OMS, PIM or PLM instead?

A WMS supports warehouse work. An ERP covers wider business processes such as purchasing and finance. An OMS manages orders, while PIM and PLM tools focus on product information and the product lifecycle. Start with the job that needs fixing. We compare your requirement with standard products, configuration and supported connections before proposing custom work. Buying a suitable product can be the right answer.

Can this work around Shopify, spreadsheets and other apps?

That is often the question worth investigating. We check what each tool owns, what access it allows and how a change can be confirmed. Availability depends on the particular product, plan and permissions. The proposed scope names the actual systems, permissions and supported actions.

How much time will our team need?

We agree that with you before building. The people doing the work need to explain a recent example, review the proposed process and test the result. Someone also needs to approve scope and system access. The plan makes those commitments visible.

We are implementing a new system. Is this too early?

Possibly. A new system needs enough use to reveal what is genuinely missing. If there is a specific blockage, bring it to the conversation. If the team is still learning the setup, keep examples of what remains awkward and what you have tried. You may need time or configuration help before another build.

Who owns the custom code?

You own your business data and the custom code we build for you. Maintenance scope and cost are agreed separately.

Start with one thing
your team keeps chasing.

Bring a recent request and show us where your team had to chase the next step. We can talk through whether there is a useful change to make.

Book Your Consultation