Custom software on the Sortly API

Sortly holds your inventory. I build the software around it.

Most teams outgrow Sortly's built-in screens long before they outgrow Sortly itself. I write the receiving tools, purchase-order flows, dashboards, and admin portals that pick up where the app stops, so your staff quit retyping the same numbers into a spreadsheet.

  • Receiving apps
  • PO intake
  • Sync jobs
  • Dashboards
  • Admin portals
  • Offline-tolerant desktop tools

What I build

Three kinds of work, and most projects touch all three.

Operator tools

Desktop and web apps for the jobs your staff repeat all day: receiving, pull lists, QA checks, transfers, relabeling a whole location at once.

Integrations

The Sortly API talking to your ERP, your accounting system, or the spreadsheet finance refuses to give up. Scheduled, retried, and logged when something fails at 2am.

Admin and access

Roles, permissions, and an admin screen so you can add a user, change what a crew can see, or cut off an account without calling me.

What changes

What actually shifts once the tooling is in place

01

Receiving stops drifting

One flow, one screen. The count that lands in Sortly is the count somebody actually took.

02

Problems surface on their own

A screen listing the eleven things that need attention today beats a monthly report nobody opens.

03

Access matches the job

Warehouse staff get the warehouse screen. Your customer sees their own items and nothing else.

04

Sortly stays the system of record

Everything I build reads and writes through the Sortly API. Your data does not get stranded inside my software.

How it goes

Three phases, and the third one is the one people skip.

I watch the work

A call or two, sometimes a site visit. I want to see the actual clicking, the actual paper, and the spreadsheet you are slightly embarrassed about.

One thing gets fixed

The first release targets whichever workflow is costing you the most hours. It ships in weeks and your team uses it right away.

Then it gets sturdy

Permissions, logging, error handling, and a support path. This is the phase that decides whether the tool is still running a year later.

Good fit

You will probably recognize yourself here.

You use Sortly every day, but half the real work still happens in Excel.

You need to show customers or crews their own slice of the data, and only theirs.

Zapier got you sixty percent of the way there and then quietly stopped.

Your team is small enough that a bad tool becomes everyone's problem by Friday.

Next step

Tell me about the worst part of your week.

No spec required. Just describe the process that keeps generating cleanup work. Receiving, POs, counts, permissions, whatever it is. If I am not the right fit, I will say so on the first call.