The booking flow distinguishes between a warning you can proceed past and a violation that blocks you outright — they're not the same thing.
Cargosender's booking flow shows two distinct kinds of message when something's wrong with the details entered: a warning, which you can review and still proceed past, and a rejection (a set of violations), which blocks the quote from going forward until the underlying issue is fixed. Confusing the two is the most common reason someone gets stuck without understanding why.
This page explains the distinction and points to the specific, verifiable rules most likely to be the actual cause — not a general 'try again' answer.
You can still get a quote — review it and proceed. It usually means something is worth double-checking but isn't invalid, and it appears as a yellow message in the booking flow.
The quote is blocked until it's fixed — a specific field doesn't meet a hard requirement. It appears as a red error tied to that specific field or rule.
It isn't a judgment about whether your item is shippable in principle — it's a specific field or rule the entered details don't currently satisfy.
It isn't the same as a booking being cancelled after payment — this happens before any payment, at the quote stage itself.
Ignoring a warning and proceeding isn't the same as a rejection being resolved — a warning is a choice to continue anyway, not a fix.
Yes — a warning lets you review the message and still proceed. It's a rejection (a violation) that actually blocks the quote until it's fixed.
Most rejections trace back to a specific field not meeting a requirement — commonly dimensions below the category's minimum, a declared value that doesn't fit the category's rule, or a route affected by sanctions. Check the entered details against the relevant category or destination guide.
Not necessarily — a rejection can come from several different rules (dimensions, declared value, route availability), of which prohibited items is only one possible cause. Check the specific message shown.
If the specific message isn't clear, ask support before repeating the same entry.
Contact Support →