Summary
π Support Location-Specific Details Across Quotes, Jobs, Invoices, Job Sheets & PDFs
π§ Improved Batched Invoices Syncing with Lightspeed β Smart "Sold by" User Selection
π οΈ Bug Fixes and Security Enhancements
π Support Location-Specific Details Across Quotes, Jobs, Invoices, Job Sheets & PDFs
We've enhanced the Store Locations feature so that location-specific details (store name, address, phone, and email) now appear on all customer-facing documents and communications. When a Store Location is set on a job or quote, all related PDFs (invoices, quotes, job sheets, water test reports) and emails will automatically use the location-specific information instead of the organisation's default details.
Key benefits:
- Location-specific details appear on all PDFs and emails when a Store Location is assigned
- Email merge tags ({org_name}, {org_address}, {org_email}, {org_phone}) automatically use Store Location details when available
- Works across single and batch invoices, quotes, jobs, and water tests
- If no location is set, the system falls back to the organisation's default details
Learn more:
π§ Improved Batched Invoices Syncing with Lightspeed β Smart "Sold by" User Selection
We've improved how the "Sold by" user is determined when syncing batched invoices to Lightspeed. The system now automatically identifies the technician who is most frequently used across all jobs linked to the invoices in the batch, ensuring a more accurate representation of who performed the work.
What changed:
- When batching multiple invoices, the system selects the technician who appears most frequently across the linked jobs
- Example: If 3 invoices are linked to jobs with Technician 1 and 1 invoice is linked to a job with Technician 2, Technician 1 will be used for the Lightspeed sync
- This provides more accurate "Sold by" information and better data consistency between Pooltrackr and Lightspeed
π οΈ Bug Fixes and Security Enhancements
Ongoing updates to ensure a smoother, safer, and more reliable user experience:
- Fixed display issues in various reporting views
- Improved error handling for failed API integrations
- Updated security protocols for API communications