This release brings two major capabilities to EQUOS: automated local printing and e-commerce integration. Together, they close the gap between online orders arriving and physical goods being picked, labelled, and shipped.
EQUOS Print — Local Print Server
EQUOS Print is a standalone Windows application that runs alongside the main EQUOS web app. It listens for print jobs via Firestore and automatically routes them to the correct local printer — no more downloading PDFs and manually printing labels.
How it works
When a user clicks “Send to Printer” in the web app (e.g., printing inventory labels or zone labels), a job is written to the Firestore print queue. EQUOS Print picks up pending jobs, processes them through the appropriate print engine, and marks them complete — all within seconds.
The app supports three printer types:
| Printer type | Use case | Example hardware |
|---|---|---|
| Thermal (ZPL) | Zone, bin, and bin location labels | Zebra GK420t |
| Label | Inventory product labels | DYMO LabelWriter |
| Standard | Invoices, pick lists, packing slips | Any A4 printer |
Queue management
The queue screen shows all print jobs with filter tabs for All, Pending, Done, and Failed states. Each job displays a summary (e.g., “5x Inventory Labels”), timing information, and status. Tapping a job opens a detail drawer with full job information and retry options.
Auto-print mode processes jobs as soon as they arrive. When disabled, jobs queue up for manual release — useful during setup or when reviewing before printing.
Workstation configuration
Each EQUOS Print installation is configured as a workstation with:
- A workstation name for identification (e.g., “WAREHOUSE-PC-01”)
- Printer profiles for each type (thermal, label, standard) mapped to system printers
- Job routing rules that direct specific job types to specific printers
- A test print button on each printer profile to verify connectivity
System tray integration
EQUOS Print runs in the Windows system tray, staying out of the way while continuously processing jobs. The tray icon shows connection status, and a context menu provides quick access to open the app or quit the service.
A connection status bar at the bottom of the queue screen displays real-time connection health, the signed-in user, and the workstation name.
Shopify Integration via Console
EQUOS now connects directly to Shopify stores, automatically importing orders into the Order Manager. The integration is managed through the console portal and uses Nango for secure OAuth authentication.
Connecting your store
- Open the Integrations page in the console portal
- Select your business (if you manage multiple)
- Click Connect on the Shopify card
- Authorise EQUOS in the Shopify OAuth flow
- The connection status updates to “Connected” with sync details
The portal shows real-time connection status, last sync time, and sync health for each connected integration.
Order sync pipeline
Once connected, Shopify orders flow into EQUOS automatically:
- Nango syncs new orders from the Shopify API on a schedule
- A webhook notifies the EQUOS backend of new data
- The Go backend fetches records, maps Shopify orders to EQUOS work orders, and writes them to Firestore
- Orders appear in the Order Manager as “send” orders, ready for fulfilment
The import pipeline handles deduplication (orders are never imported twice), SKU matching against your existing product catalog, and sequential order number assignment (WO-0001, WO-0002, etc.).
Configuration options
Each Shopify connection can be configured with:
- Order sync direction — Inbound sync from Shopify to EQUOS
- Inventory sync direction — Bidirectional sync (coming soon)
- Default location — Which warehouse location receives imported orders
Disconnecting is equally straightforward — click Disconnect in the portal and confirm. The OAuth connection is revoked immediately.
Notification System Redesign
Behind the scenes, the notification system has been rebuilt with a simpler, more scalable architecture. The previous system required multiple writes per notification and complex audience targeting. The new single-write model creates one document per event, and collectionGroup queries let each user see activity relevant to their businesses.
Key changes:
- Single-write model — One Firestore document per event, no fan-out
- CollectionGroup feeds — Cross-business activity aggregation without complex queries
- Simplified dispatcher — Modules call a single dispatch method instead of managing audience lists
- Dashboard activity feed — Combined feed showing recent activity across all accessible businesses
Freight Tab Redesign
The Transport module’s freight tab has been refreshed with new view options and better visual tracking:
- View switcher — Toggle between card, list, and table layouts depending on your workflow
- Tracking stepper — A compact widget on each freight card showing job progress through its lifecycle stages
- Effective status — Client-side status fallback ensures jobs always show meaningful status, even when carrier tracking data is delayed
The new card view makes it easy to scan active freight jobs at a glance, while the table view suits dispatchers managing high volumes of shipments.