Connect Salesforce to Posti to pull real-time shipping rates, create labels, sync tracking updates, and reduce manual fulfillment work across every order.
• Order, customer, and delivery address fields in Salesforce are mapped to Posti shipment creation payloads, including service type, parcel count, weight, and cash-on-delivery values when used.
• Shipment requests are sent from Salesforce to Posti via API, and returned identifiers are stored back on the order record, typically including shipment ID, tracking number, and label references.
• Shipping labels are generated by Posti and linked to Salesforce records; label formats and print payloads are handled per carrier-supported options.
• Tracking milestones and exception events are pulled from Posti or received via webhooks and written to Salesforce as shipment status updates and order timelines.
• Event-to-status mapping normalizes carrier-specific codes into Salesforce statuses, with timestamps preserved for customer service visibility and reporting.
• Delta updates process only changed shipments, and failed sync attempts are logged with error responses to support reprocessing and auditability.
.png)
We map Salesforce order, package, and destination data to Posti rate requests, then return available services and prices to Salesforce for selection at fulfillment time.
Yes, Salesforce can send shipment data to Posti to create labels (and customs docs when needed) and store the label URL or file back on the order or case.
Posti tracking events are pushed or polled into Salesforce and written to shipment records, so Agents see the latest status without copying tracking codes.
Typically order ID, recipient and address fields, parcel dimensions and weight, selected service, label identifiers, and tracking milestones, plus error and exception codes.
Yes, we support market-specific carrier services, formats, and rules, and keep localization logic in Salesforce so each country flow stays consistent.





