🚀 Opendock – May 2026 Release Notes

May was a month of meaningful feature work across all three product areas. We shipped the new YMS Grid View experience with full drag-and-drop support, introduced reschedule reason tracking for better accountability, expanded the check-in flow with custom form support, and made significant improvements to SmartGate reliability and accuracy. On the Gate side, we also laid the foundation for driver ID-based rejection workflows. Under the hood, a number of important security fixes, platform improvements, and SmartGate reliability fixes landed.

🏗️ What's New

Features and enhancements are organized by the three core areas of the Opendock platform. Each update includes what changed, the problem it solves, the value it adds, and where to find it.

🚪 Gate

Check-In Now Supports Multi-Language (Gate Kiosk / Comet)

What changed
The gate check-in interface (Comet) now uses the driver's default browser language to automatically display the UI in their preferred language — no manual selection required on first visit. Drivers can also manually choose a language, which will be remembered for future visits. Supported languages include English, Spanish (MX), French (CA), and Portuguese (BR). Additionally, all static UI text in Comet has been migrated to a proper internationalization framework (vue-i18n), replacing the previous third-party translation tool that caused slow page loads.

Problem it solves
Drivers arriving at facilities in Mexico, Brazil, or Canada were seeing the check-in kiosk in English by default, causing confusion and slowing down the check-in process. The old translation system also added a ~3 second delay on every page load.

Value it adds
Drivers see the check-in interface in their language the moment they arrive — no extra steps, no delays. This is especially impactful at high-volume facilities serving multilingual driver pools, and meaningfully reduces errors caused by language barriers during check-in.

Where to access
The check-in kiosk (Comet) automatically detects and applies the browser language. No warehouse configuration required.

🎬 Product Tour
[Navattic tour link — add before publishing]

Check-In Custom Form Fields Now Captured at Arrival

What changed
When a warehouse operator marks an appointment as "Arrived" and creates an asset visit from the Appointments page, the check-in now captures any custom form fields configured for the Gate & Yard → Check-in form. These custom fields appear in the create-asset dialog and are saved alongside the asset visit record.

Problem it solves
Warehouses that had custom check-in fields configured (e.g., seal numbers, reference data, commodity type) were not seeing those fields in the appointment-triggered arrival flow — only in the YMS "Add to Queue" flow. This left gaps in data capture depending on how a check-in was initiated.

Value it adds
All configured check-in data is now captured consistently, regardless of whether the arrival is triggered from the Appointments page or from the YMS. Warehouse operators get complete records without needing workarounds or manual follow-up.

Where to access
Opendock Portal → Appointments → [Select Appointment] → Change status to Arrived → Create Asset dialog

Requires check-in custom form fields to be configured under Fields & Forms → Gate & Yard → Check-in.

SmartGate: Improved Vehicle-to-Check-In Matching Logic

What changed
The way SmartGate matches an observed vehicle to a check-in has been simplified and made more accurate. When matching by license plate, it's now a strict 1-to-1 match. When matching by DOT number, the system now always matches to the earliest observation within the time window — preventing ambiguous matches when multiple trucks with the same DOT number arrive close together.

Problem it solves
In facilities where multiple trucks from the same carrier (sharing a DOT number) arrive within a short window, the old matching logic could link a check-in to the wrong observation, resulting in incorrect vehicle data appearing on check-in records.

Value it adds
More accurate vehicle-to-check-in associations mean your Gate Feed data is more reliable — the right vehicle is linked to the right check-in, reducing manual review and discrepancies in yard records.

Where to access
This improvement is automatic — no configuration needed. Affects all warehouses with SmartGate enabled.

Gate Feed: Images Now Load Reliably (DB Fallback)

What changed
When vehicle images are temporarily unavailable in the search index due to replication lag, the Gate Feed now falls back to fetching images directly from the database. This ensures images are always shown, even during brief indexing delays.

Problem it solves
Operators were occasionally seeing "awaiting images" placeholders in the Gate Feed even when images had been successfully captured — caused by a race condition where the search index hadn't yet received the images at the time of display.

Value it adds
Gate Feed entries now consistently show vehicle images on first load — no more blank placeholders or manual refreshes needed.

Where to access
Opendock Portal → Gate Feed

Foundation: Driver ID Rejection Workflow (Backend)

What changed
The backend infrastructure for rejecting a driver at check-in based on failed ID verification is now in place. This includes new asset visit event types (RejectedByCheckin, RejectedByWarehouse), a new API endpoint for handling ID-based rejections, and the database schema to support it.

Problem it solves
Warehouses using Persona ID verification had no structured way to record or report on drivers whose ID checks failed at the gate kiosk. Rejections weren't distinguishable from cancellations in reporting data.

Value it adds
Rejected check-ins are now tracked as a distinct visit status, giving warehouse operators and compliance teams a clear audit trail of which drivers were turned away and why. This is the foundation for the full rejection UI experience coming in a future release.

Where to access
This is a backend infrastructure release — the full UI experience is coming soon.

🏭 Yard

New YMS Grid View with Drag-and-Drop

What changed
The Yard Management System's Grid View has been rebuilt with a new architecture, bringing full drag-and-drop support for assets. Yard operators can now drag waiting asset cards directly to spots, drag assets from one spot to another, and see a redesigned spot grid with an updated legend and spot detail drawer.

Problem it solves
The previous grid view required multiple clicks to assign or move assets between spots. Drag-and-drop reduces the number of actions needed to manage yard traffic, especially during busy windows with multiple trucks waiting for spot assignment.

Value it adds
Yard operators can manage spot assignments faster and more intuitively — dragging a waiting asset card directly to an open spot takes one action instead of several. The updated visual design also makes it easier to read spot status and asset state at a glance.

Where to access
Opendock Portal → Yard → Grid View

The new experience is gated behind the enable-perf-improvements feature flag. Contact your Customer Success Manager to enable it.

📅 Scheduling

Reschedule Reason Now Required and Tracked

What changed
When rescheduling an appointment — from both the Helios (warehouse) portal and the Luna (carrier) scheduling portal — a reason for rescheduling is now required before confirming the change. The reason is appended to the appointment's notes and included in the rescheduled confirmation email sent to the carrier.

Problem it solves
Warehouses had no way to track why appointments were being rescheduled, making it difficult to identify recurring issues or resolve carrier disputes about who initiated a change and why.

Value it adds
Every reschedule now has a documented reason, creating an audit trail in the appointment notes. This helps warehouse managers understand scheduling patterns and gives carriers clear communication about why their appointment was moved.

Where to access
Opendock Portal → Appointments → [Select Appointment] → Reschedule
Luna → My Appointments → Reschedule

Arrival Time & Date Now Available in Custom Grid Tiles

What changed
Two new data fields — "Arrival Time" and "Arrival Date" — are now available as options in the Custom Appointments Grid tile configuration. These fields display on appointment tiles once a driver has been marked as Arrived.

Problem it solves
Warehouse staff managing live dock operations couldn't see how long a driver had been waiting without opening the appointment details, making it hard to prioritize action on drivers who had been waiting longer than expected.

Value it adds
Dock coordinators can see when each arrived driver checked in — directly on the appointment grid, without clicking into individual records. This helps teams act faster on long waits and improves the live dock management experience.

Where to access
Opendock Portal → Warehouse Settings → Custom Appointments Grid → Enable "Arrival Time" and/or "Arrival Date"

Load Type Custom Form Fields Now Copy to Recurring Appointments

What changed
When creating a recurring appointment series, Load Type custom form fields are now available as copyable fields. Operators can choose which fields to copy to all child appointments in the series.

Problem it solves
Operators using recurring appointments had to manually re-enter load type custom form data (e.g., PO numbers, commodity types, handling tags) on every child appointment — time-consuming and error-prone for high-frequency recurring shipments.

Value it adds
Set it once, and it propagates. Recurring appointment creation now handles load type form data end-to-end, saving significant manual entry time for warehouses that use recurring appointments heavily.

Where to access
Opendock Portal → Appointments → Create Recurring Series → Copy values of → Load Type Form Fields

⚙️ General Improvements

• Check-In Reporting: Updated Column Set: The asset visit reporting page now displays a cleaner set of columns: Check-in date/time, Carrier, Status, Appointment Reference Number (clickable link), Check-out date/time, Visit Type, and License Plate (for SmartGate warehouses).

• Opendock MCP: Rebuilt Tool Layer: The Opendock MCP server was fully rebuilt with role-based tool access. Carrier users, warehouse users, and internal users each see only the tools relevant to their role, enabling more reliable AI-assisted workflows. (API users: if you use the Opendock MCP, verify tool availability against the updated role-based registry.)

• WhatsApp: Argentinian & Mexican Number Handling: Incoming messages from Argentinian numbers (missing extra 9 digit) and Mexican numbers using the legacy +521 country code now correctly match to active message threads.

• Audit Log: Password Redaction on User Creation: Fixed a security issue where user passwords were stored in plain text in audit logs for INSERT operations. All entries are now correctly redacted.

• Helios: Carrier Login Blocked: Carrier users attempting to log into Helios are now correctly redirected, preventing access to the warehouse-only interface.

• Platform: Kubernetes Helm Chart Updated to 2.18.0: Improved deployment stability and compatibility.

💡 For integration users: The MCP server rebuild includes role-based gating on all tools. No breaking changes to existing API endpoints.

🐛 Bug Fixes & Stability

• OD-3615 [Settings]: Fixed a disabled feature continuing to show on the Fields & Forms page after being turned off.

• OD-3611 [Gate]: Fixed the AI Gate Feed incorrectly displaying trailer/chassis damage as "Yes" when no damage was detected.

• OD-3607 [Scheduling]: Fixed ICS calendar invites being sent when the feature flag was disabled, and being sent to the wrong user when an admin impersonated another user to create an appointment.

• OD-3604 [Gate]: Fixed the AI Gate Feed calling the observations search endpoint twice on load, causing inconsistent results.

• OD-3564 [Gate/SmartGate]: Fixed box truck number and DOT number not being persisted correctly on the vehicle entity during SmartGate automation.

• OD-3559 [Settings]: Fixed the "Enable this form" toggle and custom fields list not appearing in the Check-in form settings — a regression from a previous update.

• OD-3557 [Gate/SmartGate]: Fixed the minimum delay between SmartGate observation transmissions not being enforced correctly.

• OD-3554 [Gate]: Fixed the check-in carrier dropdown incorrectly translating company names when a non-English language was active.

• OD-3551 [Yard]: Fixed the "Add to Queue" dialog in YMS not closing after successfully creating an unplanned asset visit.

• OD-3544 [Platform]: Fixed the observation module initializing even when disabled, causing unnecessary SQS polling and event loop saturation.

• OD-3542 [Platform]: Fixed carrier users being able to log into Helios without a role check on authentication.

• OD-3527 [Gate]: Fixed an incorrect reference number at the gate kiosk redirecting drivers to an error page instead of registering them as an unplanned arrival.

• OD-3522 [Platform]: Fixed user passwords being stored in plain text in the audit log on new user creation. Historical affected entries have been remediated.

• OD-3513 [Gate/SmartGate]: Fixed the observation match time window field allowing unsafe values; now capped at 10,000 for SmartGate warehouses.

• OD-3505 [Gate]: Fixed WhatsApp 2-way messaging failing to find threads for Argentinian phone numbers.

• OD-3525 [Gate]: Fixed the same for Mexican numbers using the legacy +521 country code.

📊 What This Means for You

May's updates improve the experience at every stage — from the moment a driver arrives to how warehouse managers track their dock:

• Multilingual check-in is live → drivers in Mexico, Brazil, and Canada now see the gate kiosk in their language automatically, reducing friction and errors.

• Reschedule reasons are now tracked → every appointment change has a documented reason, giving warehouse teams better visibility and carriers clearer communication.

• The YMS grid got a major upgrade → drag-and-drop spot assignment makes live yard management faster and more intuitive.

• Custom form data is captured consistently → check-in fields now populate regardless of how an arrival is initiated.

• SmartGate matching is more accurate → fewer incorrect vehicle associations means more reliable gate data.