Equipment Times update has broken the scanner app and API integrations for warehouse workflows

1. The scanner app doesn’t match desktop

Warehouse statuses moved from the project to the packing list, which makes sense. But the scanner app hasn’t been updated to match. It only shows the default statuses, not our custom ones (“Prepped” and “Dropped off”). So the team who handle the kit can’t set the statuses that the update now relies on.

We only found this out by getting through to a technician on live chat. The release notes didn’t say anything about the app being behind.

Surely this is a mission-critical and core function for nearly all users? How on earth can it have been missed in the latest release?

2. The API has lost information with no replacement

We run our own tools on the Rentman API, including a live kit prep board for the warehouse. Before the update, subproject.status told us when a job was Prepped, On location or Returned. Since the migration it can only hold project statuses, and as far as we can see the API doesn’t expose packing lists or their warehouse status at all. Anything built on “what physical state is this job’s kit in?” has stopped working, and the API gives us nothing to rebuild it with.

What we’re asking for

  1. A date for the scanner app supporting the new warehouse statuses, including custom ones.
  2. Packing lists in the public API, with their warehouse status, pickup and return times, and the subproject they belong to.
  3. A webhook when a packing list’s warehouse status changes, so integrations can react the way they could before.
  4. Advance notice of breaking data changes for API users, sent to whoever owns the API key, before the change reaches the account.

P.s. We’re still waiting for the fix to your Stripe metadata change that we’ve raised multiple times over the last 3 months. Are these issues not more important than the dark mode you shipped recently?!

We also have issues with statuses, materials with statuses ready tp pack, packes all show as on lacation. But thats not the only issue. We can also book equipment that is not available, old projects that are totaly finished are all on "status all back in warehouse, but still to be invoiced. …

Hi @Jbez and @Mars, thanks for raising these, and sorry for the trouble. You’re right that the release notes should have said the app was behind. Here’s where things stand:

Scanner app showing the wrong statuses
This is a known issue. The current app doesn’t know the new statuses yet, so it files projects under “On location” once packing starts. We expect the app update to launch next week. Until then, the web app shows the correct status.

Packing lists in the API
Packing lists aren’t in the public API yet. I’ve passed on the request for packing list endpoints, a webhook on status changes, and advance notice of breaking changes for API key owners. You can already read warehouse statuses through the public API at /warehousestatuses and /warehousestatuses/{id}.

We’re also working on three things that bring back the “what state is this job’s kit in?” view:

  • Warehouse status column in the project overview. It counts each project’s equipment per warehouse status, for example Packed (52) / On location (335). You can see at a glance how far each job is, without opening its packing lists.
  • “Ready to pack” column in the project overview. It shows whether a project is ready to pack. For partly ready projects it shows a count, for example Ready to pack: 3/5 subprojects. Your warehouse can filter for the jobs they can start on.
  • Warehouse status per serial number in the public API. You’ll be able to see where each serial sits in the warehouse flow, for example Prepped or On location. That’s the data you need to rebuild live prep boards, dashboards or automations on a supported endpoint.

Old projects on “Execution done”
Projects that were on “Returned” moved to “Execution done” during the update. That status means all equipment is back. You set “Complete” yourself once a project is fully wrapped up. Bulk status updates through the API are coming soon.

Booking unavailable equipment
@Mars, could you DM me an example project and item? I’ll get it checked.

@Jbez, on the Stripe metadata fix. I found a bug regarding this which was fixed in 550. If you are still experiencing issues, feel free to send me a DM and we can look into if this is a different issue.

I’ll update this thread when the app is out.

Thanks Mike, that’s helpful, and good to hear the app is due next week.

On the API, /warehousestatuses only returns the list of statuses, not which project, packing list or item is on which one, so it doesn’t give us anything to work with yet. Warehouse status per serial number is the piece we need. Three questions on it:

  1. Will bulk (non-serialised) equipment get a warehouse status in the API too? A lot of our kit isn’t serialised.
  2. Will each serial’s status link to the subproject and packing list it’s on?
  3. Is there a rough timeline?

Also, could the new “Packed (52) / On location (335)” and “Ready to pack: 3/5” counts be exposed as fields on /subprojects? That would be the simplest way for integrations like ours to rebuild a prep board.

Hi Mike, adding a data point from another API user.

We raised exactly this gap with support back in July (ticket #222567). We asked whether the warehouse statuses removed from subproject.status would be exposed anywhere else, and were told the endpoints stay separate and “more communications” would come in Q4. Over 3 months later, there is still no supported way to ask the API what physical state a job’s kit is in.

To give you an idea of the real-world impact: we haven’t updated yet specifically because doing so will immediately break our daily warehouse automations. Our automated WhatsApp alerts that notify the team the moment a project is “Packed” or “Returned” will go blind. Furthermore, our automated daily “To-Be-Packed” reports will fail because both the warehouse statuses and the equipment group times have been altered or removed from the standard API payloads in the new version.

Like Jbez, we are basically stuck on standby. We know these workflows will shatter once we are forced to adapt to the changes, and currently, we have no workaround. /warehousestatuses alone does not help us; it only lists the status names, not the actual job states.

What would actually unblock us:

* Warehouse status on /projectequipment or /subprojects (including for non-serialised items).

* A dedicated packing list endpoint.

A rough timeline for these fixes would help us prepare before our current setup stops working

Thanks

Hi @Jbez and @hillel, thanks for the extra detail, and sorry this is taking longer than any of us would like. I checked with the team, and here’s where things stand.

Warehouse status in the API
We’re going to add warehouse status counts to the API at project and subproject level: how much equipment is on each warehouse status, using the same IDs as /warehousestatuses. This works from all equipment on the packing lists, so it isn’t limited to serialised items. @Jbez, this should give you what you need for a prep board.

Ready to pack
Subprojects will get a “Ready to pack” field in the next release of the API. There won’t be a total per project, like “Ready to pack: 3/5", but you can count it yourself by checking the field on each subproject in a project.

Status per item or serial number
I made this sound closer than it is in my last post, sorry. One equipment line can be split over several statuses, and adding that to every line could slow down the API a lot. So it’s not something we can promise right now. The project and subproject counts come first. I’ve also passed on the request for a packing list endpoint.

Timeline
I can’t give you a date yet. Both changes can only go live once every account has moved to the Equipment Times update. It’s high on the team’s list, and I’ll post here as soon as I have a date.

@hillel, before you update
The API endpoints didn’t change in this update, but the data did:

  • Prepped, On location and custom warehouse statuses in subproject.status become In progress, and Returned becomes Execution done. Alerts based on subproject.status for “Packed” or “Returned” won’t fire anymore.
  • Planning times now live on individual equipment items. The time fields on equipment groups still work for now but are deprecated, so a “To-Be-Packed” report should read the times per item.

Until the counts are in the API, the Warehouse status and Ready to pack columns in the project overview are the closest you can get in the web app. I know that doesn’t replace an automation.

@Jbez I just got word that the app is now live on iOS and Android if you are on C551!

Hi all,

First of all, thanks for all your input and feedback!

We just launched version 1.21.0 of the public API. In this version, we added a couple read-only fields that should give more clarity on the warehouse status of your equipment.

In short, we added the “equipment_status_quantities”-field on project, subproject and projectequipment endpoints.

The full change log can be found here: https://support.rentman.io/hc/en-us/articles/26707946497042-Rentman-API-Changelog#api-changelog-1210