Skip to main content

CEVA Logistics Accessorial Codes

18 accessorial codes for CEVA Logistics, each mapped to the service it represents and labelled with where the value came from.

Rate quote codes

Send these when requesting a rate. 14 codes.

Booking codes

Send these when creating the shipment or BOL. 4 codes.

Limits

The order-side list is documented as common values only; the schema types the field as a free string with no enumeration, so it is not exhaustive.

How codes are sent

The quote and order APIs use different codes for the same service — quote sends Inside, Room-of-Choice and White-Glove; order sends IDD, ROC and WGD.

Common questions

How many accessorial codes does CEVA Logistics have?

CEVA Logistics publishes 18 accessorial codes across pickup, delivery and shipment-level services. Each one is listed with the service it maps to and the source the value was read from.

What is the CEVA Logistics liftgate code?

CEVA Logistics uses LiftGate for liftgate delivery, sent in the ServiceTypeCode field. Other carriers spell the same service differently, so the code is only valid for CEVA Logistics.

What is the CEVA Logistics residential delivery code?

CEVA Logistics uses Res-Mil-School for residential delivery. Residential surcharges apply to any address the carrier classifies as non-commercial, which can include home businesses.

Are there limits on CEVA Logistics accessorial codes?

The order-side list is documented as common values only; the schema types the field as a free string with no enumeration, so it is not exhaustive.

How are accessorial codes sent to CEVA Logistics?

The quote and order APIs use different codes for the same service — quote sends Inside, Room-of-Choice and White-Glove; order sends IDD, ROC and WGD.

Is the CEVA Logistics accessorial code list free to use?

Yes. The lookup is free with no signup, and the same data is available from the /api/accessorials REST endpoint on every plan including the free tier.

Need this programmatically? /api/accessorials/carrier/ceva returns the same data as JSON on every plan.