Customer-facing changelog. New products, platform changes, policy updates. Newest first.
The platform has been reshaped around five banded products replacing the previous seven-SKU catalogue. The headline change customers will notice: pricing is now banded by annual spend, so smaller shippers get in and larger shippers pay fairly. Spend bands are independently verified after the first data upload.
The five v3 products:
Old product URLs (/solutions/audit, /solutions/tender, /solutions/managed, /solutions/warehouse/*) 301 to the v3 equivalents. Existing engagements on legacy SKUs continue unchanged under their original terms.
Every v3 product fees by your annual spend in the relevant category (annual freight spend for freight products, annual 3PL spend for 3PL products). Pick the band that fits at checkout. We verify the band against your first data upload; if you under-declared, we contact you to top up to the correct band before delivery. You can decline and receive a full refund.
Above A$8M annual spend, all products auto-quote within one business day. Below A$601K, tender products are not commercially recommended — the engagement size doesn't justify the work, and we'd rather tell you that than take the fee.
The customer portal has been rebuilt. Highlights:
Carriers and 3PLs invited into a tender now access their own workspace via a magic-link token. Submit DIFOT data, invoices, rate cards, manifests, or contract documents directly to the customer's analyst. Suppliers see only their own submissions; never your other suppliers, findings, or dashboards.
Real-time health checks on five customer-facing systems — public website, pricing API, Stripe checkout, customer portal, supplier portal — live at tlksource.com.au/status. Auto-refreshes every 60 seconds.
All four legal pages have been updated to reflect v3 banded pricing, the top-up flow, and our AI processing posture. Notable additions:
Behind the scenes: admin views for top-up management, supplier invite oversight, and the QA review queue. The first ten reports for each product line are routed through manual review before delivery, so any pipeline rough edges surface before customers see them.
Changelog entries reflect customer-visible changes. Internal-only changes (backend infrastructure, performance work, dependency updates) are not listed unless they affect customer experience.