Asigna Tracking

Please enter the Asigna tracking number to check the latest shipping status.

http://www.logisticacanaria.es/

About Asigna

Asigna is the carrier identity associated with shipments displayed under the Asigna name. Use the shipment identifier supplied by the sender, merchant, label, or dispatch message to retrieve available tracking events. A tracking result describes recorded scans; it does not by itself prove physical possession before an acceptance or collection scan appears.

Asigna Overview

Field	Verified resource
Official name	Asigna
Official website	http://www.logisticacanaria.es/
Tracking input	Use the shipment identifier supplied with the booking, label, receipt, or dispatch notice.
Independent tracking option	17TRACK can display tracking events made available for a recognized shipment.

Carrier Entity Relationships

Entity

Relationship to Asigna

Asigna

Asigna is the canonical carrier name used for this tracking page.

View all details for the Asigna carrier identity

Entity type	Carrier identity
Why it matters to tracking	Selecting the correct carrier helps prevent an order number or unrelated reference from being submitted as a tracking number.
Official evidence	Official website

Shipment identifier

The sender or booking workflow associates an identifier with an Asigna shipment.

View all details for shipment identifiers

Entity type	Tracking product
Why it matters to tracking	The tracking number, order number, and merchant reference can be different identifiers.
Official evidence	Use the identifier displayed by the booking or shipping channel.

Customs and delivery handlers

Where a shipment crosses borders or uses a delivery handoff, another responsible entity may create later events.

View all details for handoff entities

Entity type	Network, customs, or last-mile participant
Why it matters to tracking	Electronic shipment data, physical custody, customs review, and final delivery are separate stages.
Official evidence	The shipment record and latest scan identify the relevant stage.

17TRACK

17TRACK independently aggregates available tracking events and does not transport Asigna shipments.

View all details for the 17TRACK relationship

Entity type	Independent tracking platform
Why it matters to tracking	17TRACK can organize shipment events but cannot alter delivery, customs, address, refund, or claim decisions.
Official evidence	17TRACK API documentation

Quick Answer

To track an Asigna shipment, copy the shipping identifier from the dispatch message, label, receipt, or merchant account and enter it on the official website or 17TRACK. If no result appears, first remove spaces added during copying, distinguish the tracking number from the order number, and allow time for the first physical acceptance scan. 17TRACK is an independent tracking platform; it cannot transport a parcel, change an address, authorize a refund, or approve a claim.

Pro Tip: A shipment record created electronically does not prove that Asigna has received the physical parcel. Look for an acceptance, collection, processing, or facility scan before assigning physical custody.

How to Track Asigna Packages

Track through the official Asigna website when you need the carrier-facing record, or use 17TRACK when you want a normalized timeline alongside shipments from other carriers.

Find the shipment identifier in the dispatch email, shipping label, receipt, merchant order page, or sender’s shipping system.
Copy the identifier exactly. Remove surrounding spaces, but retain letters and meaningful internal characters.
Open the official Asigna website and use the available shipment lookup path.
Alternatively, enter the same identifier on 17TRACK and select Asigna if automatic carrier recognition needs confirmation.
Read the latest event together with its time, location, and lifecycle stage rather than relying on the status headline alone.

Which Identifier Should You Use?

Identifier	How to use it
Tracking or shipment number	Use this first for shipment tracking.
Order number	Use it in the merchant’s account unless the merchant explicitly labels it as the carrier tracking number.
Merchant reference	Ask the sender to map it to the shipment number if the carrier lookup rejects it.
Label or barcode value	Use it only when the shipping document identifies that value as trackable.
Delivery notice reference	Use it for the instructions printed on the notice; it may differ from the original shipment identifier.

Asigna Tracking Number Formats and Examples

Use the complete identifier supplied for the shipment rather than guessing from a prefix. An identifier that appears in an Asigna result may have originated in a merchant, booking, or partner workflow, so successful lookup does not necessarily identify the issuing party.

Tracking Number Format

Identifier family

Normalized pattern

Asigna shipment identifier

Enter the complete value exactly as supplied; remove only surrounding or clearly decorative spacing.

View all details for the Asigna shipment identifier

Length/structure	Rely on the shipment document rather than an inferred length or prefix rule.
Issued by	The shipment booking or label workflow associated with the consignment.
Typical service/use	Consumer or business shipment lookup.
Who sees it and where	Senders may see it on a booking record or label; recipients may see it in a dispatch message or merchant account.
Tracking scope	Available events associated with that identifier.
Important caveat	A prefix alone should not be treated as conclusive proof of service type, route, or current custodian.

Merchant order or reference ID

Example: ORDER-####-XXXX; use only as a masked illustration, not as a carrier format.

View all details for merchant references

Length/structure	Defined by the merchant’s order system.
Issued by	Merchant or marketplace workflow.
Typical service/use	Order support, payment records, and sender-side shipment matching.
Who sees it and where	Buyers see it in order confirmations and account history.
Tracking scope	Usually limited to the merchant system unless explicitly mapped to a shipment.
Important caveat	An order number is not automatically an Asigna tracking number.

Handoff or delivery identifier

Use the later identifier only when it is explicitly linked to the same shipment.

View all details for handoff identifiers

Length/structure	Determined by the receiving delivery system.
Issued by	The participant creating the linked delivery record.
Typical service/use	Later-stage delivery or local handling.
Who sees it and where	It may appear in later tracking events, a delivery notice, or sender support records.
Tracking scope	Often begins at or near handoff.
Important caveat	Electronic pre-advice is different from physical transfer and a linked number does not prove receipt.

Asigna Tracking Statuses and Meanings

Interpret an Asigna status as a record of the latest available event, not as a continuous location feed. The event text, timestamp, facility, and preceding scan together identify the shipment’s likely lifecycle stage.

Status Quick Lookup

Status

What it means

Shipment information received

Electronic data exists, but physical acceptance may still be pending.

View all details for shipment information received

Lifecycle stage	Pre-shipment
Current responsible party	The sender remains responsible until a physical acceptance event appears.
What happens next	Collection, drop-off, or an acceptance scan.
What you should do	Ask the sender when the parcel was physically handed over if the status persists.

Accepted or collected

The parcel has entered the handling network recorded for the shipment.

View all details for accepted or collected

Lifecycle stage	Accepted
Current responsible party	The entity shown by the acceptance or collection scan.
What happens next	Sorting and routing to the next facility.
What you should do	Monitor for the next processing event.

In transit or processed

The shipment is moving through sorting, transport, or transfer stages.

View all details for in transit

Lifecycle stage	In transit
Current responsible party	The facility or transport operator associated with the latest event.
What happens next	Arrival, departure, handoff, or destination processing.
What you should do	Compare the elapsed time with the shipment-specific estimate and recent scan pattern.

Customs processing

The shipment or its data is undergoing an import, export, security, or document process.

View all details for customs processing

Lifecycle stage	Customs or handover
Current responsible party	The customs authority, broker, declarant, or custodian identified by the event.
What happens next	Release, information request, assessment, inspection, or return decision.
What you should do	Respond promptly if the carrier, sender, or customs representative requests documents or payment.

Out for delivery

The parcel has entered a delivery route, but delivery is not yet complete.

View all details for out for delivery

Lifecycle stage	Out for delivery
Current responsible party	The delivery unit or driver shown by the route event.
What happens next	Delivery, attempted delivery, pickup instruction, or exception.
What you should do	Ensure access, address visibility, and any required recipient availability.

Delivered

A completion scan was recorded at the destination or an authorized delivery point.

View all details for delivered

Lifecycle stage	Delivered
Current responsible party	The delivery record identifies completion; the recipient should verify the delivery location.
What happens next	The shipment closes unless a delivery dispute is opened.
What you should do	Check the address, safe locations, household members, reception, neighbors, and any proof of delivery before escalating.

Available for pickup

The parcel is being held at the location named in the tracking event or notice.

View all details for available for pickup

Lifecycle stage	Pickup
Current responsible party	The pickup location named in the event.
What happens next	Recipient collection or return after the applicable holding process.
What you should do	Follow the notice and bring the required identification and shipment information.

Delivery exception

A condition such as access, address, weather, damage, or operational disruption prevented normal progress.

View all details for delivery exception

Lifecycle stage	Exception
Current responsible party	The entity controlling the stage described in the exception event.
What happens next	Reprocessing, another attempt, customer instruction, investigation, or return.
What you should do	Read the full event and contact the sender or Asigna when an instruction or correction is required.

Returning to sender

The shipment has entered a reverse route and is no longer progressing toward the original recipient.

View all details for returning to sender

Lifecycle stage	Return
Current responsible party	The return custodian shown by the latest scan.
What happens next	Reverse transport and delivery back to the sender or return address.
What you should do	The recipient should contact the merchant; the sender should monitor the return and decide whether to refund or reship.

Asigna Services and Delivery Times

The applicable service and delivery expectation are defined by the shipment booking, origin, destination, acceptance time, and any customs or handoff stage. Use the service description and estimate attached to the individual shipment rather than applying a generic transit promise.

Service Comparison

Service

Best for

Booked Asigna shipment service

The parcel, document, commercial, or delivery use stated in the booking record.

View all details for the booked Asigna service

Service type	Use the exact service shown on the label, receipt, contract, or shipment confirmation.
Coverage	Defined by the booked origin and destination.
Tracking level	Depends on the scans generated during collection, processing, transport, handoff, and delivery.
Key size/weight condition	The accepted limits are those applied during booking and acceptance.
Included protection/extra service	Only the protection or additional service stated in the shipment contract applies.
Main limitation	A tracking event does not expand the booked service, protection, or delivery commitment.

Delivery Time

Service

Published delivery standard

Shipment-specific Asigna booking

Use the delivery estimate or service terms attached to the individual booking.

View all delivery-time details for an Asigna booking

Business or calendar days	Apply the counting method stated in the booking or service terms.
Guarantee status	An estimated date or window is not a guarantee unless the booked terms expressly make it one.
Starts counting from	Use the acceptance point defined by the booked service, not merely label creation.
Main delay factors	Late handover, weekends, holidays, weather, capacity, address quality, remote delivery, customs, security review, and handoff timing.
Official source date/validity	Check the current booking confirmation and official Asigna website for the shipment’s applicable terms.

Destination Country Delivery Times

Destination Country / Region

Estimated Delivery Time Range

Destination stated in the Asigna booking

Use the route-specific delivery estimate supplied for the booked shipment.

View all destination delivery details

Primary Service Type	The service named in the booking or label.
Average Delivery Days	Judge current progress from the shipment-specific estimate and actual scan history rather than an unsupported route average.
Last-Mile Partner / Handoff Carrier	Use the entity identified by the latest handoff or delivery event.
Customs & Clearance Tips	Ensure the item description, value, recipient data, and requested import documents are complete; arrival in a destination region does not mean customs release.

Delivery estimates can change after acceptance as new operational information becomes available. A displayed estimate, delivery window, service standard, and guaranteed commitment are different concepts and should not be used interchangeably.

Common Asigna Tracking Problems and Solutions

Start with the latest scan, identify who physically controlled that stage, and then contact the party able to act. Recipients usually need the sender’s help for booking changes, value evidence, refunds, and contractual claims.

Problem & Solution

Problem/status shown

Immediate action

Invalid number or no result

Re-copy the identifier and distinguish it from the order number.

View all details for an invalid Asigna number

Likely cause	Copying error, merchant reference, early registration, or carrier-selection mismatch.
Check first	Letters, digits, spaces, and the sender’s dispatch message.
When to escalate	When the sender says physical handover occurred but the identifier remains unusable.
Who to contact	The sender first, then Asigna with the shipment record.

Shipment information received

Ask the sender whether physical handover has occurred.

View all details for pre-shipment

Likely cause	A label or electronic record exists before collection or acceptance.
Check first	The sender’s actual handover date.
When to escalate	After the sender confirms handover and no physical scan appears within the shipment’s expected processing pattern.
Who to contact	The sender, because the sender controls the handover evidence.

No update or stuck in transit

Compare the last location and elapsed time with the booked estimate.

View all details for a tracking gap

Likely cause	Transport between scans, batch processing, missed scan, weekend, disruption, or handoff.
Check first	The latest timestamp, location, exception text, and delivery estimate.
When to escalate	When the estimate has passed or the event expressly requests action.
Who to contact	Asigna for operational tracing; the sender for a contractual investigation.

Handoff pending

Wait for the first physical receipt scan by the receiving entity.

View all details for a pending handoff

Likely cause	Electronic pre-advice was sent before physical transfer.
Check first	Whether the event says data received, tendered, departed, or physically accepted.
When to escalate	When the handoff gap exceeds the shipment estimate or an exception appears.
Who to contact	The entity holding the parcel before physical transfer, or the sender if custody is unclear.

Address problem or failed delivery

Read the event for redelivery, pickup, or sender-contact instructions.

View all details for delivery failure

Likely cause	Incomplete address, access restriction, recipient absence, or route condition.
Check first	The delivery address and any notice left for the recipient.
When to escalate	Immediately when a correction or collection deadline is stated.
Who to contact	Asigna for delivery instructions; the sender when a contractual address change is required.

Customs delay

Respond to document, value, identity, or payment requests.

View all details for customs delay

Likely cause	Review, assessment, inspection, incomplete declaration, restricted goods, or importer action.
Check first	Messages sent to the recipient, sender, or declarant.
When to escalate	When an information deadline is approaching or the event directs contact.
Who to contact	The requesting authority, broker, sender, or Asigna according to the notice.

Delivered but not received

Check the delivery location, household, reception, neighbors, and proof of delivery in that order.

View all details for delivered but not received

Likely cause	Safe-location delivery, reception acceptance, neighbor delivery, address mismatch, or scan dispute.
Check first	The exact address, timestamp, named recipient, delivery note, and surrounding property.
When to escalate	Promptly after local checks fail.
Who to contact	Asigna for delivery evidence and the sender for an order remedy or formal investigation.

Lost or damaged shipment

Preserve the parcel, contents, packaging, labels, photographs, and value evidence.

View all details for loss or damage

Likely cause	Handling damage, missing contents, delivery dispute, or an unresolved transit gap.
Check first	The booked protection, shipment terms, tracking history, and sender’s proof of value.
When to escalate	As soon as loss or damage is identified and before disposing of evidence.
Who to contact	The sender or contracting account holder and Asigna through the official channel.

Returning to sender

The recipient should contact the merchant; the sender should monitor the return.

View all details for a return to sender

Likely cause	Delivery failure, refusal, incomplete address, customs outcome, or uncollected shipment.
Check first	The first return event and its reason.
When to escalate	When the reason appears incorrect or a merchant remedy is needed.
Who to contact	The merchant or sender for refund or reshipment; Asigna for tracking clarification.

Asigna International Shipping, Customs and Carrier Handoffs

When an Asigna shipment includes an international or inter-jurisdictional movement, electronic pre-advice, physical custody, customs control, and last-mile delivery remain separate responsibilities. Arrival at a destination gateway does not mean customs release or final delivery.

International Flow

Stage

What is happening

Shipment creation

The sender creates shipment data and prepares the parcel.

View all details for shipment creation

Physical custodian/responsible entity	The sender until collection or acceptance.
Typical tracking event	Shipment information received.
Can the tracking number change?	A later linked identifier may appear if another handling system is used.
Normal visibility gap	Between electronic creation and the first physical scan.
What the customer should do	Ask the sender for the physical handover date if no acceptance event appears.

Origin acceptance and processing

The parcel is accepted, sorted, and routed toward an export or transfer point.

View all details for origin processing

Physical custodian/responsible entity	The entity shown by the acceptance and facility events.
Typical tracking event	Accepted, processed, or departed facility.
Can the tracking number change?	The original identifier commonly remains searchable, while linked references may be added.
Normal visibility gap	During transport between facilities.
What the customer should do	Monitor unless an exception requests action.

Export or security process

Shipment data and goods may undergo export, aviation-security, or regulatory controls.

View all details for export processing

Physical custodian/responsible entity	The current logistics custodian and relevant authority.
Typical tracking event	Export processing, security review, or departure preparation.
Can the tracking number change?	A transport or declaration reference may coexist with the customer-facing identifier.
Normal visibility gap	While regulatory or transport processing occurs.
What the customer should do	Ensure the sender supplied accurate contents, value, and documentation.

Line-haul transport

The shipment moves between origin and destination gateways.

View all details for line-haul transport

Physical custodian/responsible entity	The contracted transport custodian for that movement.
Typical tracking event	Departed, in transit, or transport arranged.
Can the tracking number change?	Internal transport references may be added without replacing the customer-facing number.
Normal visibility gap	Between departure and gateway arrival scans.
What the customer should do	Wait for the next gateway or destination event unless the estimate has passed.

Import customs

Authorities may assess declarations, restrictions, duties, taxes, or supporting documents.

View all details for import customs

Physical custodian/responsible entity	The customs-controlled custodian and relevant authority.
Typical tracking event	Presented to customs, under review, information requested, or released.
Can the tracking number change?	A customs or broker reference may be added.
Normal visibility gap	Review duration depends on the shipment and authority process.
What the customer should do	Respond to document or payment requests through the stated official channel.

Partner handoff

Electronic data may precede physical transfer; responsibility changes only when custody is actually transferred.

View all details for partner handoff

Physical custodian/responsible entity	The dispatching entity before transfer and the receiving entity after a physical acceptance scan.
Typical tracking event	Pre-advice received, tendered, handed over, or accepted.
Can the tracking number change?	A linked last-mile number may be introduced.
Normal visibility gap	Between electronic notification, transport arrival, and receiving scan.
What the customer should do	Use the latest physical scan to identify custody rather than assuming pre-advice equals receipt.

Last mile and delivery

The destination delivery unit sorts the parcel to a route, pickup point, or final address.

View all details for last-mile delivery

Physical custodian/responsible entity	The entity identified by the destination acceptance or delivery event.
Typical tracking event	Arrived at delivery unit, out for delivery, available for pickup, attempted, or delivered.
Can the tracking number change?	The original or a linked delivery identifier may be used.
Normal visibility gap	Between destination sorting and route scans.
What the customer should do	Follow any delivery, access, pickup, or identification instructions.

Asigna Delivery Management and Post-shipment Options

A delivery change is effective only when Asigna accepts it for the specific shipment. The sender may control contractual changes, while the recipient may be limited to instructions offered in the tracking event or delivery notice.

Delivery Management

Option

Who can request

Delivery instruction or address review

The sender or recipient according to the booking and current shipment stage.

View all details for delivery instructions

Eligibility	Depends on identity checks, service terms, route status, customs status, and fraud controls.
Deadline/available stage	Request action before final delivery or return processing makes the change impractical.
Fee	Any fee is determined through the official service channel.
Guaranteed?	No request should be treated as completed until Asigna confirms acceptance.
Official action link	Official Asigna website

Redelivery or pickup response

The named recipient or authorized person following the shipment notice.

View all details for redelivery or pickup

Eligibility	Follow the options and identification requirements shown in the event or notice.
Deadline/available stage	Act while the parcel remains in the delivery or holding process.
Fee	Check the official instruction associated with the shipment.
Guaranteed?	Availability depends on the parcel’s current location and route status.
Official action link	Official Asigna website

Asigna Lost, Damaged, Claims, Insurance and Refunds

A tracking inquiry, transport investigation, damage claim, insurance claim, shipping-charge refund, and merchant refund are separate processes. The contracting sender or account holder commonly holds the booking evidence and should preserve all documents needed under the applicable shipment terms.

Claims and Refunds

Process

Use when

Tracking inquiry or transport investigation

Use when tracking is inconsistent, overdue, or missing a meaningful next event.

View all details for an Asigna tracking inquiry

Who files	The sender, contracting customer, or recipient where accepted.
Earliest/latest filing time	Use the current service terms and act when the shipment estimate or stated action point is reached.
Required evidence	Tracking number, booking date, sender and recipient data, service, contents description, and latest event.
Possible outcome	Tracking clarification, location attempt, request for information, delivery continuation, return, or claim guidance.
Official link	Official Asigna website

Loss, damage, or missing-contents claim

Use when the shipment is declared lost, arrives damaged, or arrives with contents missing.

View all details for an Asigna claim

Who files	The party entitled under the booking or transport contract, often the sender or account holder.
Earliest/latest filing time	Follow the current service-specific terms immediately after discovering loss or damage.
Required evidence	Shipment record, value proof, item description, photographs, labels, outer and inner packaging, and contents.
Possible outcome	Investigation, request for more evidence, settlement under applicable terms, or denial.
Official link	Official Asigna website

Merchant refund or replacement

Use when the buyer seeks an order-level remedy from the seller.

View all details for a merchant remedy

Who files	The buyer contacts the merchant under the order policy.
Earliest/latest filing time	Use the merchant’s purchase-protection or return timeframe.
Required evidence	Order number, tracking history, delivery dispute details, photographs, and correspondence.
Possible outcome	Refund, replacement, further investigation, or rejection under the sales terms.
Official link	Use the merchant account or order-support channel associated with the purchase.

17TRACK cannot approve an Asigna claim, issue a refund, determine liability, or change the transport outcome.

Asigna Shipping Restrictions and Special Handling

Restrictions depend on the booked service, route, transport mode, and applicable law. The sender must declare contents accurately and obtain acceptance before tendering goods that are hazardous, regulated, perishable, high-value, or subject to import and export controls.

Shipping Restrictions

Asigna Customer Service

Use the official Asigna website for current contact and shipment-support options. Contact the sender first when the issue concerns an order number, handover evidence, commercial refund, declared value, or a claim that must be filed by the contracting customer.

Customer Service

Channel

Verified contact/link

Official website

http://www.logisticacanaria.es/

View all details for the official Asigna website

Best for	Current shipment lookup, service information, and available contact routes.
Region/language	Use the options presented on the official website.
Hours and time zone	Follow the hours displayed by the selected official contact channel.
Information to prepare	Tracking number, booking date, sender and recipient details, service, latest scan, contents description, value evidence, and photographs where relevant.
Important limitation	Identity, contract, customs, and sender-authorization checks may limit what can be disclosed or changed.

Sender or merchant support

Use the order account, receipt, or sales-support channel associated with the purchase.

View all details for sender or merchant support

Best for	Order-number mapping, proof of handover, refunds, replacements, invoices, declared value, and sender-filed investigations.
Region/language	Determined by the sales channel.
Hours and time zone	Follow the merchant’s support information.
Information to prepare	Order number, tracking number, purchase date, item description, delivery address, and screenshots of relevant events.
Important limitation	The merchant can address the sales contract but cannot rewrite carrier scans or customs decisions.

A practical escalation order is: verify the identifier and latest scan, contact the sender for booking evidence, use the official Asigna channel for operational tracing, and preserve written records and physical evidence if a formal claim may follow.

Asigna Ecommerce and Business Tracking

Businesses should retain the mapping between each order number, Asigna shipment identifier, customer, service, and any later handoff identifier. 17TRACK can support multi-carrier tracking workflows, while the official Asigna channel remains the source for carrier-specific operational action.

Developer/API Comparison

Option

Provider

Official shipment lookup and support

Asigna

View all details for official Asigna tracking access

Carrier coverage	Asigna shipment records available through the official channel.
Primary use	Consumer lookup and carrier-specific shipment support.
Authentication	Follow the access method presented by the official website or commercial agreement.
Tracking/batch/webhook capability	Use only capabilities included in the applicable official account or agreement.
Current developer documentation	Official Asigna website
Migration/deprecation note	Implement only against documentation supplied for the current integration.

Multi-carrier Tracking API

17TRACK

View all details for the 17TRACK API

Carrier coverage	Multi-carrier tracking through 17TRACK’s supported carrier network.
Primary use	Shipment registration, normalized tracking visibility, and multi-carrier workflows.
Authentication	API requests use the 17token header as documented by 17TRACK.
Tracking/batch/webhook capability	Use the capabilities and limits described in the current 17TRACK API documentation.
Current developer documentation	17TRACK API documentation
Migration/deprecation note	Use the documented current API version and review release or migration notices before deployment.

Asigna FAQ

1. How do I track my Asigna package?

Enter the shipment identifier from the dispatch notice, label, receipt, or merchant account on the official Asigna website or 17TRACK. Read the latest event together with its timestamp and lifecycle stage.

2. Where can I find my Asigna tracking number?

Look in the shipping confirmation, merchant order page, label, booking receipt, or sender’s shipping system. If you only have an order number, ask the sender to provide the linked Asigna shipment identifier.

3. What does an Asigna tracking number look like?

Use the complete identifier explicitly labeled for shipment tracking rather than relying on a guessed prefix or length. Order references, barcode values, and later delivery identifiers may serve different purposes.

4. When will the first Asigna tracking event appear?

The first meaningful physical event appears after collection, drop-off, or acceptance is scanned. Electronic shipment information can appear earlier and does not prove that the parcel has entered physical custody.

5. Why is my Asigna tracking not updating?

A gap can occur during transport, batch processing, weekends, operational disruption, customs review, or a handoff. Compare the latest event with the booked estimate and escalate when the estimate passes or an action message appears.

6. How long does Asigna delivery take?

Use the shipment-specific estimate attached to the booked service. Acceptance time, destination, holidays, weather, remote delivery, customs, and handoffs can affect the result, and an estimate is not automatically a guarantee.

7. What should I do after a failed Asigna delivery attempt?

Read the complete event or delivery notice for redelivery, pickup, access, or address instructions. Act promptly if the shipment is being held or may enter a return process.

8. What should I do if Asigna says delivered but I cannot find the parcel?

Verify the address and check safe locations, household members, reception, neighbors, and available proof of delivery. If those checks fail, contact Asigna for delivery evidence and ask the sender to support a formal investigation.

9. How do I report a lost or damaged Asigna shipment?

Preserve the parcel, contents, packaging, labels, photographs, booking records, and proof of value, then contact the contracting sender and Asigna through the official channel. Do not discard evidence before the claim process is resolved.

10. How do I contact Asigna?

Use the current support routes presented on the official Asigna website. Prepare the tracking number, booking date, service, addresses, latest scan, contents description, and supporting evidence before contacting support.

11. Does shipment information received mean Asigna has the parcel?

No; it usually means an electronic record exists. Physical custody should be inferred only after an acceptance, collection, processing, or equivalent possession scan appears.

12. Can an Asigna shipment receive another tracking number after handoff?

A linked identifier can appear when another handling or delivery system creates its own record. Keep both identifiers and use the latest physical acceptance event to determine which entity currently holds the parcel.

13. Does arrival at a destination gateway mean an Asigna shipment cleared customs?

No; gateway arrival, presentation to customs, customs release, and destination delivery are separate events. Wait for an explicit release or onward-processing event and respond to any document or payment request.

14. Who is responsible during an Asigna partner handoff?

The dispatching entity remains the likely physical custodian until transfer occurs, while the receiving entity becomes responsible after a physical receipt scan. Electronic pre-advice alone does not establish that transfer.

15. Can businesses track Asigna shipments through an API?

Businesses can use 17TRACK’s multi-carrier API for supported tracking workflows and should use only current official integration documentation supplied for any direct Asigna connection. Keep order, shipment, and handoff identifiers mapped separately.

16. Can 17TRACK change an Asigna delivery or approve a claim?

No; 17TRACK is an independent tracking platform that displays available events. Address changes, delivery instructions, investigations, claims, and refunds must be handled by Asigna, the contracting sender, or the merchant as applicable.

Asigna Tracking API

Use current documentation supplied through an official Asigna integration agreement for any direct carrier connection. The example below shows the documented 17TRACK registration request; retain the carrier placeholder until the applicable 17TRACK carrier code is verified in the account or current documentation.

See the 17TRACK API documentation for authentication, request limits, responses, and current integration guidance.

# 1. Asigna official tracking API
# Use only current endpoint, method, authentication, and request fields
# supplied through an official Asigna integration agreement.

# 2. 17TRACK API: register a tracking number
curl --request POST \
  --url https://api.17track.net/track/v2.4/register \
  --header '17token: YourKey' \
  --header 'Content-Type: application/json' \
  --data '[
    {
      "number": "TRACKING_NUMBER",
      "carrier": "CARRIER_CODE"
    }
  ]'