# Gsped codes ## Type of payment - COD | COD Code | Description | | :------: | :----------------------------------------------------: | | 10 | Cashier's cheque payable to the original sender | | 11 | Accept cashier's cheque payable to the original sender | | 12 | Cash only | | 15 | Accept dated cheque payable to the original sender | ## Shipment status codes | Status Code | Description | Notes | | :---------: | ------------------------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------- | | -1.0 | REQUESTED | Assigned to GSped shipments before the confirmation, driven by API (no interface) | | 0.0 | CREATED | assigned to properly created shipments, it becomes visible after the shipment confirmation | | 0.2 | DEFERRED DEPARTURE | for specific needs, driven by API (no interface) | | 0.3 | TO BE AUTHORISED | for specific needs , driven by API (no interface) | | 0.5 | IN PROCESS | rarely used, assigned to the queued shipments that are still to be labeled, driven by API (no interface) | | 0.6 | PROCESSED WITH ERRORS | assigned to the shipments with labeling errors, driven by API (no interface) | | 1.0 | SENT | assigned to pickup requests that have been correctly transmitted to the courier (this applies to couries such as BRT to which we send a file) | | 2.0 | RECEIVED | assigned to pickup requests that have been confirmed by the courier | | 3.0 | SENT TO THE RELEVANT BRANCH | assigned to pickup requests | | 4.0 | CONFIRMED | assigned to pickup requests | | 5.0 | PICKUP | assigned to pickup requests | | 6.0 | COLLECTED | assigned to pickup requests | | 7.0 | NOT YET COLLECTED: LACK OF TIME | assigned to pickup requests | | 8.0 | NOT YET COLLECTED: PARCEL NOT READY | assigned to pickup requests | | 9.0 | NOT YET COLLECTED: CUSTOMER NOT FOUND/CLOSED | assigned to pickup requests | | 10.0 | CANCELLED BEFORE THE COLLECTION | assigned to pickup requests | | 11.0 | CANCELLED: REJECTED BY THE CUSTOMER | assigned to pickup requests | | 12.0 | CANCELLED: ALREADY COLLECTED | assigned to pickup requests | | 12.1 | CANCELLED: NOTHING TO COLLECT | assigned to pickup requests | | 13.0 | CANCELLED: Goods not available in the warehouse | assigned to pickup requests | | 14.0 | CANCELLED: CUSTOMER NOT FOUND AT THE GIVEN ADDRESS | assigned to pickup requests | | 15.0 | CANCELLED: WRONG TELEPHONE NUMBER OR NO ANSWER | assigned to pickup requests | | 16.0 | CANCELLED: TWO ATTEMPTS MADE | assigned to pickup requests | | 16.5 | UNCLAIMED | assigned to pickup requests | | 17.0 | SHIPMENT ON ITS WAY | departure confirmed by the courier | | 17.4 | ARRIVED AT THE BRANCH | the shipment has arrived at its destination branch | | 17.5 | SHIPPING IN TRANSIT | Goods in transit | | 17.6 | STORED FOR REASONS OF FORCE MAJEURE | the goods have been storaged in depots | | 17.7 | HOLD FOR PICKUP | additional service: the shipments could be picked up from the courier's office | | 17.8 | HOLD FOR PICKUP FOR CAUSES NOT DEPENDENT ON THE COURIER | shipment storaged due to strikes, adverse weather conditions or otherwise. | | 18.0 | TO BE DELIVERED | goods taken in charge by the courier for the delivery | | 18.1 | CLOSED FOR TURN | recipient not available for the delivery | | 18.4 | ARRIVED AT THE PICK-UP POINT | (only with BRT) the shipment has arrived at the Fermopoint | | 18.5 | PARTIAL DELIVERY | only a part of the parcels has been delivered. | | 19.0 | DELIVERED | the goods have been delivered | | 19.1 | RETURNED TO SENDER | for shipment returned to the sender | | 20.0 | REROUTED | arrived to the wrong branch and subsequently rerouted | | 20.5 | ABSENT | the recepient is absent | | 21.0 | RETURNED TO SENDER FROM THE BRANCH | when the shipment is returned to the sender from the the branch | | 30.0 | IN STORAGE | the goods remain in stand-by, waiting for release | | 31.0 | RELEASED FROM STORAGE | when the courier confirms the release of the goods or the shipment is on it way | | 32.0 | REFUSED BY THE RECIPIENT | the goods have been refused by the recipient- | --- # Agent Instructions: Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter: ``` GET https://apidocs.gsped.com/gsped-api-english-version/overview/codici-gsped.md?ask= ``` The question should be specific, self-contained, and written in natural language. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.