Shipment portals
Estimate normal and peak lookup traffic. Separate the needs of a public tracking page from the systems that update shipment records.
Choose server resources for the applications that connect shipment information, warehouse activity and customer-facing delivery updates.
Estimate normal and peak lookup traffic. Separate the needs of a public tracking page from the systems that update shipment records.
List database, storage and software requirements for the applications you operate. Include scheduled imports and reporting workloads in the resource estimate.
Document API endpoints, authentication, update frequency and retry behavior. Identify which upstream systems are required for a complete shipment workflow.
Test from the networks and devices used by field teams. Check how your application handles delayed connections and repeated submissions.
Compare RAM and storage performance for transaction-heavy databases, and CPU needs for imports and reporting. Choose a location with the application’s users and partner connections in mind. For a physical server requirement, compare dedicated configurations; otherwise assess the cloud plans against the same workload measurements.
Use the server comparison to review the two server types, or explore country and city guides for location options.
Create a test shipment, update its status and verify the customer view and partner notifications.
Test queued imports and repeated API messages so application behavior remains predictable after a connection is restored.
Decide who can restore the service and how recent records will be reconciled after recovery.
The standard dedicated and cloud plans are presented as unmanaged. Assign responsibility for the operating system, applications, updates, monitoring and backups. Review server management responsibilities and use the deployment checklist to plan the move.
Compare the current configurations and prices, then review your product, location, options and final total in the cart.