Two companies can enter the same package and destination and see different UPS pricing. That is not necessarily an error. Business shipping accounts can have account-specific incentives or negotiated pricing based on the customer’s UPS relationship.
Published rate vs. negotiated rate
A published rate is the carrier’s standard rate structure before account-specific incentives. A negotiated rate reflects pricing associated with a particular shipping account or agreement. The final transportation charge can also be affected by service, zone, dimensional weight, accessorial charges, fuel, and other shipment details.
Why the shipping account matters
UPS developer documentation explains that account numbers are used in rating and shipping contexts and can be associated with shipper-level incentives. In practice, that means software needs the correct account context when requesting rates intended to reflect a business’s pricing.
Should customers see your negotiated UPS rates?
That is a commercial and contractual question, not merely a software setting. Businesses should review their carrier agreement and decide what rate information each type of user should see. A platform can technically support different rate views, but the business still needs rules governing what is appropriate.
Why this matters for customer portals
If customers are creating shipments through a business relationship, rate presentation becomes part of the customer experience. Some organizations may pass through shipping cost. Others may use a customer-specific charge, handling fee, allowance, or other pricing model. The system should make the chosen model consistent and auditable.
Do not confuse rate shopping with rate governance
Rate shopping asks, “Which available service costs less?” Rate governance asks, “Which rates is this user allowed to see, which services can they choose, and what amount should be presented to them?” Businesses managing external users often need both.
Shipping access should match the way your business actually works.
SubShipper is being built for organizations that need controlled shipping across customers, dealers, partners, locations, and fulfillment relationships—without turning one carrier login into the operating system for everyone.