Shipping & deliveries (Correos — in preparation)

What happens today

All orders are collected in person at our office in Puerto de Santiago (Tenerife). We do not ship to your home yet.

Prices in the shop include IGIC. There are no Correos shipping charges at checkout until home delivery is switched on.

What we are preparing (Canary Islands only)

We are integrating Correos so we can offer home delivery within the Canary Islands first. Scope, prices and lead times will be confirmed before we turn the option on in checkout.

This page summarises the technical process we follow on our side. It is not a commercial offer from Correos; your contract and tariffs are always with Correos under your client account.

How Correos API access works

You request access in the Correos API Exchange / portal for each API (e.g. Preregister). The request is reviewed; when approved, Correos sends credentials by email.

APIs can have different usage levels (SLA) and sometimes cost. Security can be: no auth (rare), Client ID + Client secret as HTTP headers, or JWT Bearer tokens from CorreosID (see their documentation).

Our Next.js shop will store client id and secret only in server environment variables (never in the browser). JWTs, if required, will be obtained server-side and refreshed as documented by Correos.

Preregister API (shipments)

Base URL (example from documentation): https://api1.correos.es/admissions/preregister/api/v1

Available operations: preregister one or more shipments (sender, recipient, packages, add-ons, customs data where applicable); retrieve shipment data by preregistration codes; cancel a shipment; modify shipment data.

Limit: up to 100 packages per online preregistration request. For higher volumes, Correos provides a bulk flow (mass processing).

Example endpoint family (HTTPS): POST /delivery, POST /delivery/cn, POST and PUT /delivery/package, POST /delivery/package/iris, POST /delivery/annulment, POST /delivery/annulment/expedition — exact payloads are in Correos’ technical spec.

• Labels, tracking (Trackpub), and webhooks (Track&TracePush) are separate APIs you enable as needed.

Product codes (summary — full table is Correos Annex I)

Correos assigns each “product” a code (e.g. PAGXC Paq Ligero, PAFXB Paq Estándar, PADXA Paq Premium). Each has limits on weight, dimensions, and number of packages. For bike parts and accessories we will usually choose a parcel product that fits weight/size and delivery mode (home, office, CityPaq, etc.).

Example rows from the official table: Paq Ligero (PAGXC) up to 2000 g; Paq Estándar home delivery (PAFXB + DOUAOF) up to 40 kg per package; Paq Premium (PADXA) for stricter service levels. Large or palletised items use different products (e.g. pallet services).

Merchandise content type uses numeric codes (e.g. 513 = bicycle parts) for customs/declaration where required.

Delivery modes (abbreviations)

Examples from Correos documentation: home delivery (DOUAOF), office delivery (OFUAOF), reference office (ORUAOF), CityPaq (CIUAOF), mailbox deposit (BUUAOF), returns (DOURUA), curbside (PCUAOF), etc. The product + mode combination must be valid in their catalogue.

Canary Islands in Spain

Spanish province codes used in addresses include 35 (Las Palmas) and 38 (Santa Cruz de Tenerife). Our shop and Correos flows will use valid postcodes and recipient data for domestic Spain shipments within the islands.

OAuth redirect URIs (optional)

If Correos or CorreosID uses a browser OAuth flow, register redirect URLs such as https://www.kudo-shop.com/api/integrations/correos/oauth/callback and http://localhost:3000/api/integrations/correos/oauth/callback for development. If the integration is server-only (client credentials), you may not need redirect URIs.

Disclaimer

Information on this page is a condensed summary for transparency. Binding rules, prices, and technical behaviour are always those in your Correos contract and in the official API documentation. Until we announce home delivery in checkout, collection at our office remains the only option.