2026.05.05May 5, 2026

New Booking workflow sidebar in Admin, more reliable attachments, and modernized customer, provider, and product forms

This release introduces a brand-new Booking workflow sidebar in Admin that mirrors the field experience, makes attachment uploads more reliable across the platform, modernizes the customer, provider, and product forms, hardens authorization and data integrity, and refines bookings, incidents, and external integrations.

Products updated: Admin · Network Web · Provider Web · Platform API · Product API · Event Manager

Booking workflow sidebar (Admin)

New

A brand-new Booking workflow sidebar is now available on the booking detail in Admin, mirroring the experience already used by providers in the field. From a single panel, operators can advance the service through every stage.

Workflow steps. Creation → Scheduling → Displacement → Finalization, with the active step always visible.
Step-by-step action buttons. Start service, On my way to origin, Arrived to origin, On my way to destination, Arrived to destination, Leave destination, Add evidence, Complete checklist, Create budget, Finalizing actions, and Finalize service.
Checklist drawer. Complete checklist steps and fields directly from the booking, with progress preserved between sessions.
Add evidence drawer. Attach photos and documents tied to the booking workflow, using the new upload reliability behavior described below.
Client signature drawer. Finalize a service with the customer's signature — either by uploading a signed document or by drawing the signature on the screen.
Product unit confirmation. Confirm the specific units being delivered, including a "Confirm new serial number" flow with a clear validation message ("Serial number does not match") and a confirmation dialog ("Serial number {N}. This action cannot be undone. Do you wish to continue?") before applying the change.
Finalize with warehouse selection. When finalizing the service, choose the destination warehouse where the product will be stored: "Select the warehouse where the product will be stored."
Dynamic forms on status changes. When a status transition requires extra information, a dedicated drawer collects it inline as part of the workflow.

Attachment uploads — more reliable across the platform

Upload-first strategy on incident creation. Across Admin, Network Web, and Provider Web, attachments are now uploaded as you add them rather than at submit time. This makes incident creation faster and avoids losing the form if a file fails partway through.
Clear error feedback. When one or more files fail, users now see "Some attachments failed to upload. Please try again." and can retry without re-entering the rest of the form.
Same lifecycle on every dropzone. All file dropzones (incidents, budgets, leads, tasks, notes, evidence, etc.) now use the same upload-and-track behavior, so the in-progress / done / failed states are consistent everywhere.

Bookings & Incidents

Stakeholders ("Requestors") cleanup. The "Add requestor" helper is more explicit: it adds a person, different from the client, who will be contacted and notified about the service progress and acts as the main contact for the field technician. The stakeholder filter on bookings and the stakeholder fields on creation/edit handle requestors more reliably (fixes edge cases where filters or types were inconsistent).
Incident status display fix. The status select on incident creation now always shows the correct value (previously could appear blank or out of sync in some flows).
Incident creation — extra fields. New optional fields surfaced on the incident drawer: Full name, Identification number, and Comments, with consistent placeholder hints.
Booking history — Reference field. When adding a detail to a booking, you can now record a Reference — useful for linking a booking to an external order, ticket, or document number.
Faster admin product confirmation. Confirming a product unit from Admin no longer triggers an unnecessary provider lookup, making the action noticeably faster.

Customer & Provider forms

Modernized customer creation form. The customer creation flow in Admin now uses the new controlled inputs introduced in the previous release (cleaner validation, faster typing, consistent country/phone selectors).
Modernized provider form. Same migration applied to the provider creation/edit form on Admin and Network Web — same look and feel as customers.
Modernized product forms. Product creation and component creation drawers in Admin migrated to the new controlled inputs.

Product catalog (Admin)

Empty description allowed on product update. You can now clear the product description on edit (previously the empty value was rejected).
Advanced configuration drawer fixes. The loading skeleton orientation is correct, and editing a product whose description is empty no longer breaks the form.

Provider Web — error handling

New "We couldn't load this section" page. When a part of the app fails to render, providers now see a friendlier message with a "Try again" action and a "Reference code" they can share with support: "The application ran into a problem while rendering this view. Try again in a few seconds."

External integrations

Update an incident's external reference. Partners can now keep their own reference number on an existing incident in sync via the integration API, so cross-system traceability stays accurate even when references change on the partner side.
Sodimac integration improvements. Routine catalog and origin parsing have been tightened on the integration layer, reducing edge cases when ingesting Sodimac orders into Sodtrack.

Reliability & data integrity

Provider availability lookups no longer time out. On accounts with very large service-variant catalogs (Network Web "available days" calendar and provider variant lookups in particular).
Unique customer/user identifiers. The platform now enforces uniqueness on user.reference and stakeholder.reference end-to-end, including pre-validation that returns a clear conflict message before any data is written. Empty strings are normalized to "no reference" automatically. Action required: before this change goes live for your tenant, ensure no two active records share the same external reference (the migration audits this and will surface any conflicts).
Authorization hardening. Network operators can now act on a provider only when they actually own that relationship (new ownership check on network → provider access). Permissions across the platform are now homologated with Auth0 to keep roles in sync.

Ready to see Sodtrack in action?

Book a demo and our team will walk you through the latest features tailored to your operation.