SigniQ v1.4.2 Release Notes

Date: 31-03-2026

This release introduces major platform enhancements with a strong focus on asset-based bookings, timezone accuracy, and event-driven integrations. It also includes important backend refactors to improve reliability and scalability.

What Changed & Why It Matters

Asset Booking Support (Services → Assets Evolution)

What changed

• Introduced full support for bookable assets alongside services
• New APIs, DB models, and proxy layers to handle asset bookings
• Unified booking flow for services and assets
• Asset support across:
  • Booking pages (customer + admin)
  • Promotions, deposits, and offers
  • Pricing and credit calculations
  • “My Bookings” view
• Generic QR code support (target_type, target_id)
• Sidebar and UI updated to support asset grouping and navigation

Why it matters

• Expands platform capability beyond services → supports rooms, equipment, rentals, etc.
• Unified architecture reduces duplication and simplifies future feature development
• Enables richer business use cases with minimal additional configuration

Timezone & DST-Aware Booking System

What changed

• Introduced timezone support in availability and booking APIs
• Added timezone field to availability (with migration)
• Updated frontend + backend logic to respect timezone context
• DST-aware availability calculations
• Removed start_time and date from API inputs (handled server-side)

Why it matters

• Eliminates inconsistencies caused by cross-timezone bookings
• Ensures accurate availability during daylight saving transitions
• Moves critical time logic to backend → reduces client-side errors

Event-Driven Integrations (Widget → Parent Communication)

What changed

• Widgets now emit booking events to parent pages
• Enhanced websocket event handling and reload logic
• Improved event payloads (includes tenant_id, user_id)
• More robust booking event triggering logic

Why it matters

• Enables analytics, ad tracking, and custom integrations
• Makes the platform more extensible for embedded use cases
• Ensures reliable real-time updates across systems

Booking & Payment System Refactor

What changed

• Renamed and standardized:
  • service_offer → payment_offer
  • Unified credit & offer handling
• Refactored pricing, credit, and payment calculations
• Improved webhook handling for payments and bookings
• Removed unnecessary deposit fetch logic
• Better handling of credits in booking flows

Why it matters

• Cleaner and more consistent API design
• Reduces ambiguity between services vs payments
• Improves correctness in pricing, offers, and notifications

Smarter Booking Logic & Data Integrity

What changed

• Prevent duplicate/overlapping booking slots
• Improved event triggering logic based on booking outcome
• Validation improvements (tenant_id, availability inputs)
• Auto-fill missing user details in bookings
• Generic booking tracker updated to support assets

Why it matters

• Ensures data consistency and reliability
• Prevents edge-case bugs in scheduling
• Improves auditability and system correctness

Infrastructure & Migration Improvements

What changed

• Introduced automated DB init + migration system
• New migration scripts for:
  • Timezone support
  • Payment offers
• Moved DB initialization to a centralized service
• Dependency and Node version upgrades

Why it matters

• Simplifies deployment and environment setup
• Ensures schema consistency across environments
• Reduces operational overhead for upgrades

UI/UX Enhancements

What changed

• Asset filtering in widgets
• Booking modal height fixes
• Consistent navigation (back/next UX)
• Help page updates + in-app help links
• Improved theme consistency and defaults
• Sidebar grouping for better navigation

Why it matters

• Cleaner, more intuitive user experience
• Better usability for both customers and staff
• Improved visual consistency across the platform

⚠️ Important Notes

• Booking APIs no longer accept start_time and date → handled internally
• Availability now requires timezone awareness (migration applied)
• API naming updates (payment_*) may require client adjustments

Summary

v1.4.2 is a foundational upgrade that:

• Expands the platform to support assets as first-class entities
• Fixes long-standing timezone and DST issues
• Introduces event-driven extensibility
• Strengthens backend architecture for future scale