SwiftX Express Tracking

Track a SwiftX Express package on this page

Use the carrier tracking number shown in one of these places:

• the seller’s shipment confirmation;
• the marketplace order page under carrier or delivery information;
• a SwiftX notification;
• a shipping label;
• the official SwiftX tracking page;
• an upstream logistics record that explicitly maps a destination number to SwiftX.

Enter one supported carrier number at a time. Do not enter:

• a marketplace order number;
• a merchant reference;
• a recipient name;
• an email address or phone number;
• a full street address;
• a building or gate code;
• a customs reference;
• a support ticket;
• a return authorization;
• a proof-of-delivery image;
• an identity document;
• payment or card information.

A tracking number may expose facility names, dates, locations, delivery events, and the final outcome. Treat it as private shipment information. Do not publish the complete number in a review, screenshot, forum post, page title, public URL, analytics label, or unnecessary AI prompt.

Which SwiftX identifier should you enter?

One observed SwiftX number family

One current indexed result from the official SwiftX tracker used a 21-character identifier with this structure:

SWX##################

That is:

• SWX;
• followed by 18 digits.

This is an observed official example, not a complete specification. SwiftX has not published one universal:

• total length;
• prefix list;
• check digit;
• country code;
• numeric range;
• historical format;
• partner-number rule;
• regular expression.

Do not reject a number solely because it differs from the masked example, and do not accept a number solely because it begins with SWX.

SWX does not prove the carrier identity

The letters SWX are not a safe stand-alone carrier lock. Similar acronyms, internal references, and unrelated Swift-branded businesses exist.

Use several identity anchors together:

• the seller or marketplace explicitly names SwiftX or SwiftX Express;
• the number is recognised by the official swiftx-express.com tracker;
• the current tracking provider maps it to SwiftX;
• the event history is consistent with the same shipment;
• the number is not an order ID, return reference, customs reference, or another carrier’s number.

When the carrier remains unclear, use the original seller record or find the last-mile carrier before relying on one prefix.

What is SwiftX Express?

SwiftX is a technology-driven parcel network created for the U.S. ecommerce market. Current official and government sources identify the U.S. entity as SWIFTX Inc. The public brand is SwiftX, while consumers and carrier directories commonly use SwiftX Express.

Official materials describe a network that can involve:

• first-mile pickup;
• warehouses and sorting;
• linehaul;
• regional delivery operations;
• Delivery Service Providers, or DSPs;
• employees and contractors;
• temporary or crowdsourced delivery personnel;
• package scans;
• route tasks;
• delivery records;
• proof-of-delivery photography;
• exception documentation.

This operating model creates several important distinctions:

The SwiftX brand, SWIFTX Inc., a warehouse, a DSP, an assigned driver, an origin carrier, a customs actor, the seller, and the marketplace are not interchangeable parties.

A SwiftX tracking event can be produced through SwiftX systems even when a contracted delivery partner or driver performs the physical task. That does not make the merchant the carrier, the driver the claims authority, or the facility a public pickup point.

SwiftX is not SpeedX

SwiftX and SpeedX are different carrier identities.

Do not use a logo, provider code, support link, or tracking form from a similarly named company.

Legal name and address caution

The official public privacy policy and the FMCSA record support the name SWIFTX Inc. The internal driver-app privacy notice uses SwiftX Express Inc. This page treats SwiftX Express as the recognisable carrier name rather than declaring a second separately verified legal entity.

Current official and platform sources also expose addresses in Eastvale and Ontario, California. They may serve different corporate, operational, registered, or developer functions. Neither address is presented here as a customer pickup depot.

United States scope and cross-border boundary

SwiftX describes its mission around the U.S. ecommerce market. Its current privacy policy says the website and services are intended for U.S.-based users.

The same policy states that users in the European Union, European Economic Area, and United Kingdom must not use the official website. This is an unusual but material jurisdiction boundary. The official tracker link on this page is therefore identified as the current U.S. carrier site, not as a universal global service.

SwiftX also uses cross-border and global-logistics language. That can describe a route in which the shipment begins outside the United States and enters a SwiftX destination network later. It does not prove that SwiftX:

• accepted the parcel in the origin country;
• controlled the export carrier;
• operated the international flight;
• acted as the customs authority;
• decided customs release;
• handled every data event;
• offers worldwide recipient service.

A cross-border parcel may follow a sequence such as:

seller or marketplace
→ export warehouse
→ origin carrier or consolidator
→ international linehaul
→ customs authority or broker
→ United States gateway
→ SwiftX shipment record
→ SwiftX facility receipt
→ warehouse and regional processing
→ DSP or driver route
→ recipient

This is an actor model, not a guaranteed route for every SwiftX parcel.

From order creation to a SwiftX delivery event

Does SwiftX have the package?

A recognised record is not physical possession

The official tracker can recognise a number before the public history contains a facility-receipt event.

Recognition confirms:

• the number is readable in the SwiftX tracking environment;
• a shipment record exists;
• public fields or events may be available.

Recognition does not confirm:

• that SwiftX has physically received the parcel;
• that the item has entered a SwiftX warehouse;
• that an assigned driver has it;
• that customs has released it;
• that the package is moving;
• that the seller completed handoff.

This distinction is especially important for cross-border ecommerce. A destination-carrier number can be created before the parcel reaches the destination network.

Shipment Received at Facility is stronger evidence

In a current indexed official SwiftX result, Shipment Received at Facility appears as a public event.

The strongest safe interpretation is:

SwiftX recorded that the shipment was received at a facility.

This is stronger evidence of physical network receipt than:

• an order marked shipped;
• an SWX prefix;
• number recognition;
• destination-carrier assignment;
• customs clearance;
• an upstream carrier event.

It still does not prove:

• what happened during every earlier stage;
• the parcel’s live position now;
• the condition or contents at receipt;
• which employee, contractor, or DSP handled it;
• the exact next departure time.

For the broader possession boundary, see Carrier Received Package.

SwiftX tracking statuses and event evidence

SwiftX has not published a complete public consumer status dictionary. The following guide uses event names observed in a current official tracking result and separates them from broader last-mile phrases that may appear on individual records.

Observed official SwiftX events

These labels come from an observed official result. They must not be presented as every possible SwiftX status or as one universal sequence.

Shipment Received at Facility

This is the clearest observed public possession milestone.

Possible next stages can include:

• sorting;
• relabeling;
• warehouse processing;
• dispatch;
• linehaul;
• regional transfer;
• delivery-route assignment;
• an exception.

The public event does not tell you which of those actions is already complete.

Arrived At Warehouse

This event identifies a recorded warehouse arrival.

A warehouse can be:

• an origin-side processing node;
• a regional sorting location;
• a destination facility;
• an operational staging point.

The wording does not establish that the parcel is available for collection. SwiftX has not published a general recipient facility-pickup policy or a public depot directory.

Do not travel to an address found in a job listing, map result, company registration, driver-app record, or tracking event unless current official support gives a shipment-specific collection instruction.

In Transit

In Transit is a broad network state. It can cover movement or processing between recorded checkpoints.

It confirms that SwiftX’s public system classifies the parcel in a network stage. It does not show:

• continuous movement;
• a live vehicle;
• a driver’s route;
• every intermediate scan;
• a guaranteed delivery date;
• that a repeated label means no physical change occurred.

Public tracking is event-based. Internal operational systems may hold more detailed timestamps and location records than the recipient-facing page.

For cross-carrier interpretation, see In Transit.

Out for Delivery or another final-route event

The research did not find a complete official SwiftX glossary defining every final-route phrase. When the exact record says Out for Delivery or shows another delivery-route event, the safest interpretation is:

SwiftX’s system recorded a final-mile route stage for that shipment.

It does not guarantee:

• delivery that day;
• delivery within a fixed hour;
• a nearby-driver alert;
• live driver GPS;
• access to the driver;
• successful building entry;
• a secure placement location.

Use Out for Delivery for the broader evidence model. If the route closes without delivery, use Out for Delivery but Not Delivered.

Failed, refused, restricted-entry, or attempted-delivery wording

Users may see a SwiftX record that refers to:

• failed delivery;
• refused delivery;
• restricted entry;
• no access;
• an address issue;
• an exception;
• return movement.

SwiftX has not published a complete public reason dictionary or universal attempt policy. Read the exact event rather than replacing it with a generic label.

A carrier-recorded attempt or reason confirms what the SwiftX system recorded. It does not independently prove that:

• the driver reached the correct building or unit;
• the address was correct;
• the recipient refused the parcel;
• the recipient caused the failure;
• building access was impossible;
• the parcel will be retried automatically.

Preserve the full wording, timestamp, address record, and any lawful private evidence. Report a disputed event through official support without accusing a driver or recipient from one scan alone.

For the cross-carrier classifier, see Delivery Attempted.

Delivered

Delivered means SwiftX recorded a completed delivery outcome.

It does not, by itself, prove:

• the named recipient personally received the parcel;
• the item was placed at the correct apartment or unit;
• the pictured location was authorised;
• the package was undamaged;
• every ordered item was present;
• the parcel remained at the location after placement;
• theft, misdelivery, or driver misconduct;
• that a merchant refund or payment dispute is resolved.

A Delivered event is carrier evidence. It is not the complete answer to a delivery dispute.

Why SwiftX tracking may not update

The latest evidence stage determines which party can investigate.

The number is not recognised

Check:

• every letter and digit;
• whether you entered an order number instead of a carrier number;
• whether another carrier is named;
• whether the seller has only created a destination record;
• whether the number is newly issued;
• whether SWX was confused with SPX;
• whether SwiftX and SpeedX were confused.

Ask the seller or marketplace to identify the exact carrier and provide the carrier number. Use Tracking Number Not Found when no usable carrier record appears.

The record exists, but no facility-receipt event appears

The parcel may still be:

• with the merchant;
• at an origin warehouse;
• with another carrier;
• in international linehaul;
• in customs;
• awaiting U.S. destination injection;
• waiting for the first public SwiftX receipt event;
• affected by delayed data publication.

The unchanged record cannot identify which explanation applies. Before a SwiftX facility receipt, the merchant or upstream logistics provider is usually better placed to confirm the physical handoff.

A SwiftX facility or warehouse event exists

SwiftX possession or processing is now more strongly attributable.

A later gap can reflect:

• sorting;
• linehaul;
• regional transfer;
• route capacity;
• exception handling;
• delayed public synchronization;
• a missing or corrected scan;
• a return workflow.

No current official source establishes a universal number of hours or days after which one unchanged SwiftX event proves loss.

Preserve the timeline, contact official SwiftX support, and keep the merchant or marketplace informed because the merchant controls the commercial order remedy.

The package is cross-border

Compare:

• the marketplace order;
• the origin-carrier number;
• the SwiftX number;
• the latest customs or gateway event;
• the expected date;
• any merchant, marketplace, card, or payment-provider deadline.

A SwiftX number can become visible before SwiftX physically receives the parcel. Customs clearance can also precede SwiftX facility receipt.

For a broader decision path, see Tracking Not Updating and How International Package Tracking Works.

Delivery estimates, delivery hours, and service promises

SwiftX has not published a current public consumer table establishing one universal:

• transit-time range;
• delivery-by hour;
• weekend schedule;
• holiday schedule;
• route cutoff;
• service class;
• guaranteed delivery date;
• late-delivery remedy.

Marketing language about speed, national growth, technology, or real-time visibility is not an item-level service commitment.

Use:

• the latest attributable carrier event;
• the merchant’s current order estimate;
• any service commitment shown in the transaction;
• the current official support response.

Do not infer a delivery schedule from community posts, driver observations, job descriptions, or one tracking history.

Delivery attempts and redelivery

No current public SwiftX source reviewed establishes a universal:

• number of delivery attempts;
• next-attempt date;
• automatic redelivery rule;
• return-to-sender threshold;
• holding period.

Therefore, this page does not promise that SwiftX will try once, twice, three times, or on the next business day.

When an attempt event appears:

1. read the exact reason;
2. verify the address and unit on the merchant order;
3. preserve the event and timestamp;
4. use SwiftX’s current official support route;
5. alert the merchant or marketplace when return or refund rights may be affected;
6. keep external dispute deadlines active.

A support inquiry does not prove that a new attempt has been scheduled.

Address, access codes, hold, and pickup

Address changes

No current public recipient address-change policy was found.

Use the merchant or marketplace for:

• a wrong city;
• wrong state;
• wrong ZIP code;
• wrong recipient;
• material destination change;
• order cancellation or reroute request.

Use current official SwiftX support to report an active delivery problem, but do not assume SwiftX can change the contractual destination after shipment.

Building and access information

An apartment, gated community, concierge desk, parcel room, or commercial property may require private access details.

Do not publish:

• gate codes;
• entry instructions;
• intercom codes;
• personal phone numbers;
• hidden placement directions.

Submit only necessary information through the current official support route. A submitted access code does not guarantee that the route record was updated before the next attempt.

Hold and facility pickup

No current official general hold or recipient pickup policy was found.

A tracking event that names a warehouse or facility does not mean:

• the package is available;
• the site accepts visitors;
• the address is a customer counter;
• staff can release the parcel;
• identity verification or pickup is supported.

Do not visit a SwiftX address without explicit shipment-specific authorization from current official support.

Direct driver contact and live location

SwiftX’s internal driver system can use route and location data. That does not create public access to:

• live driver GPS;
• the driver’s phone number;
• internal task notes;
• exact route order;
• private scan location.

11Tracking cannot expose or retrieve those records.

SwiftX proof of delivery and internal evidence

Current official driver-application materials show that SwiftX’s operational system can support:

• package scans;
• delivery status records;
• timestamps;
• route data;
• GPS-linked records;
• proof-of-delivery photos;
• exception photos or videos;
• device and user activity.

A July 2026 SwiftX Driver update specifically refers to Smart POD improvements, blur detection, and camera guidance for higher-quality delivery photos.

This supports an important conclusion:

SwiftX can create richer internal delivery evidence than the public status label alone.

It does not establish that:

• every shipment has a photo;
• every photo has precise GPS;
• every recipient can view the photo;
• every evidence object is retained for the same period;
• a recipient can retrieve route data;
• the evidence is independently verified;
• one photo legally resolves every dispute.

What a POD photo can support

A photo may help compare:

• the doorway or building;
• the placement location;
• the surrounding surface;
• visible unit or address clues;
• the package label or shape;
• the time associated with the record.

A photo does not automatically prove:

• recipient identity;
• correct address or unit;
• authorisation of the location;
• item contents;
• package condition;
• continued possession after the image;
• whether a later theft or retrieval occurred.

Use Proof of Delivery for the broader evidence framework.

Evidence privacy

Delivery evidence can expose:

• a home or building entrance;
• an apartment number;
• a label;
• a neighbour’s property;
• a person;
• a vehicle;
• a precise place and time.

Keep it private. Do not upload a delivery photo, signature, tracking number, full address, access code, or GPS data to a public review or forum.

SwiftX says Delivered, but the package is missing

Start with the strongest available evidence, not an accusation.

1. Read the complete Delivered event and location wording.
2. Check any delivery image or note only through SwiftX’s current official route.
3. Compare the image with:

• the front or side entrance;
• mailroom;
• parcel room;
• front desk;
• concierge;
• neighbouring unit;
• garage;
• safe placement area.

1. Ask other household or building members.
2. Preserve the timeline, image, merchant order, and lawful building evidence.
3. Report the missing delivery to SwiftX through its current official support page.
4. Contact the merchant or marketplace for its refund, replacement, or buyer-protection process.
5. Observe card, payment-provider, and marketplace deadlines even while SwiftX reviews the event.

Keep these questions separate:

• Did SwiftX record Delivered?
• Where does the available evidence point?
• Did the named recipient personally receive it?
• Can SwiftX review the carrier record?
• Can the merchant issue a refund or replacement?
• Is a payment dispute deadline approaching?

A carrier investigation and a merchant remedy can proceed on separate tracks.

Use Delivered but Not Received for the full recovery sequence.

Return to sender or reverse movement

SwiftX has not published a complete public return-to-sender policy.

When the exact tracking record shows reverse movement, the strongest safe interpretation is:

SwiftX recorded that the shipment entered a return stage.

That does not prove:

• the merchant has received it;
• the merchant has inspected it;
• the return was accepted under the order policy;
• a refund was approved;
• payment has been returned;
• the buyer’s external deadline is paused.

Contact both:

• SwiftX, for the current carrier event and whether the movement can still change;
• the merchant or marketplace, for the order, replacement, refund, or return decision.

Do not use a merchant return authorisation as a SwiftX carrier number unless the official tracker recognises it.

Claims, refunds, and who can act

No current public SwiftX claims, liability, insurance, compensation, or recipient-eligibility policy was found in the reviewed official material.

The official customer-service form creates an inquiry route. It does not, by itself, prove:

• that the recipient can file a contractual carrier claim;
• that SwiftX accepts liability;
• a filing deadline;
• a compensation amount;
• an insurance limit;
• a refund promise.

Keep the processes separate.

A carrier record can inform a merchant decision without replacing the merchant’s commercial responsibility.

For the general evidence and actor model, see Package Claim Guide and Who to Contact About a Package.

Contact SwiftX customer service

Use SwiftX’s current official Customer Service page for a shipment-specific issue.

The official site currently also lists:

• email: contact form;
• telephone: +1 909-268-7835.

Contact details, form fields, response wording, file limits, and availability can change. Verify them on the official page before relying on them.

Prepare:

• the SwiftX tracking number;
• the exact latest event;
• the timestamp;
• the displayed location;
• a concise description of the problem;
• the merchant order number for merchant support;
• any necessary private delivery evidence.

Do not send more information than the case requires. Avoid sharing:

• card or bank data;
• account passwords;
• one-time codes;
• unrelated identity documents;
• full building-security credentials;
• unredacted evidence in a public channel.

A submitted support form does not guarantee a specific response time, correction, redelivery, refund, claim decision, or parcel recovery.

Privacy: tracking, support forms, and driver records

SwiftX’s current website privacy policy describes the main site as a limited U.S. tracking platform and discusses technical data such as IP address, browser information, cookies, and usage data.

The live official site also provides support, contact, and partner forms that request information such as:

• email;
• tracking number;
• name or company information in some contexts;
• message;
• optional attachments.

Those live forms make the policy’s broad statements about not collecting personal information incomplete as a description of every current website interaction.

Practical rule:

Review the current official form and privacy notice before submitting evidence, and provide only the information necessary for the shipment issue.

SwiftX’s internal driver-app policy describes a different operational environment that may record:

• driver or contractor identity;
• device information;
• package number;
• status;
• timestamp;
• GPS;
• route data;
• delivery photos;
• exception media.

That internal evidence is not part of the public 11Tracking form and must not be exposed in metadata, analytics, public URLs, or screenshots.

Verify suspicious SwiftX messages

A message can mention a real carrier or a real tracking number and still be fraudulent.

Treat a message cautiously when it:

• asks for an unexpected fee;
• requests card details;
• demands a one-time code;
• uses a lookalike domain;
• claims an urgent address problem without a matching official event;
• asks for an identity document through an unfamiliar link;
• threatens immediate return unless payment is made.

Safer verification:

1. do not use the message link;
2. open swiftx-express.com independently;
3. check the exact number and event;
4. use the current official customer-service page;
5. contact the merchant through the original order;
6. do not disclose passwords, card data, or one-time codes.

A valid SwiftX number authenticates the carrier record, not the sender of every text or email.

Use Fake Delivery Message for the broader scam-verification process.

SwiftX coverage and facility claims

SwiftX’s company and recruiting materials describe rapid expansion, warehouses, regional operations, DSP management, pickup operations, dispatch, sorting, and linehaul across multiple U.S. locations.

Those materials help explain the network model. They do not create a public promise that:

• every ZIP code is served;
• a named city handles your parcel;
• a job-listed warehouse is permanent;
• a facility accepts recipients;
• the package can be collected there;
• a specific route or capacity is available.

The current public evidence does not provide a complete consumer ZIP-coverage tool or public facility directory.

Use the seller’s carrier assignment and the official SwiftX tracker for the shipment-specific record.

Frequently asked questions

Is SwiftX Express a real carrier?

SwiftX operates an official tracking and support website under swiftx-express.com. Current official and government sources identify the U.S. entity as SWIFTX Inc. The network is positioned around U.S. ecommerce and last-mile delivery.

Is SwiftX the same as SpeedX?

No. SwiftX and SpeedX use different official domains, entity names, tracking systems, and identifiers. Do not interchange their logos, provider codes, support pages, or tracking numbers.

What carrier uses an SWX tracking number?

One current official SwiftX example uses SWX followed by 18 digits. The prefix alone is not sufficient proof because Swift-related names and internal references can collide. Confirm the carrier through the seller, official domain, or a verified provider response.

How many digits are in a SwiftX tracking number?

One observed official example has 21 characters: SWX plus 18 digits. SwiftX has not published a complete universal format specification, so do not treat 21 characters as the only valid format.

Can I use my marketplace order number?

Usually not. The marketplace order number belongs to the purchase record. Use the separate carrier tracking number explicitly attributed to SwiftX.

Does a recognised SwiftX number mean SwiftX has my package?

No. Recognition proves that a SwiftX-readable record exists. A later event such as Shipment Received at Facility is stronger evidence of recorded SwiftX receipt.

What does Shipment Received at Facility mean?

It means SwiftX recorded receipt at a facility. It does not reconstruct the complete earlier route, provide continuous location, or prove final-route assignment.

What does Arrived At Warehouse mean?

SwiftX recorded a warehouse-arrival event. It does not mean the parcel is available for public pickup or that processing is complete.

What does In Transit mean?

It is a broad recorded network stage. It does not show continuous GPS, one vehicle, uninterrupted movement, or a guaranteed delivery time.

Does Out for Delivery guarantee delivery today?

No. When that exact event appears, it records a final-delivery route stage. Access, route, address, capacity, or operational issues can still prevent completion.

How many delivery attempts does SwiftX make?

No current public universal attempt rule was found. Read the exact event and contact official SwiftX support and the merchant when the shipment may be returned.

Can I pick up a package from a SwiftX warehouse?

No general public pickup policy was found. A warehouse event or job-listed facility is not a public collection instruction. Do not travel to a facility without explicit shipment-specific authorization.

Can SwiftX change my delivery address?

No current public recipient address-change policy was found. Contact the merchant or marketplace for a material destination error and use official SwiftX support to report the active delivery issue.

Does SwiftX take delivery photos?

Current official driver-app materials show that SwiftX’s internal system supports POD photographs and other delivery evidence. They do not prove that every shipment has a photo or that every recipient can access it.

Does a SwiftX delivery photo prove I received the package?

No. A photo may support a recorded placement event, but it does not automatically prove the named recipient, correct unit, contents, condition, authorisation, or continued possession.

What should I do if SwiftX says Delivered but I have no package?

Review the complete event and any available delivery evidence, check likely building locations, preserve the records, report the issue to SwiftX, and contact the merchant or marketplace for its refund or replacement process.

Can I file a claim directly with SwiftX?

The reviewed public material does not establish universal recipient claim eligibility. The official support form can start an inquiry, while a contractual transport claim may belong to the shipper. Keep merchant and payment deadlines active.

Does SwiftX handle customs?

SwiftX discusses cross-border logistics, but no current public evidence establishes that it is the customs authority or controls every clearance decision. Use the exact customs event and responsible broker, merchant, or authority.

Why does SwiftX’s privacy policy restrict EU, EEA, and UK users?

The current official policy says the website and services are intended for U.S.-based users and directs EU, EEA, and UK users not to use the site. This page does not override that restriction.

Can 11Tracking contact SwiftX or the driver?

No. 11Tracking can display supported public tracking events. It cannot contact SwiftX or a driver, access internal GPS or POD, change a delivery, file a claim, issue a refund, or recover a package.

Use USTracking as a tracking companion

USTracking may help display supported public SwiftX events alongside other carrier records when a shipment changes networks.

It cannot:

• establish SwiftX identity from SWX alone;
• create a missing scan;
• access internal SwiftX route or GPS data;
• retrieve private POD photos;
• contact SwiftX, a DSP, or a driver;
• change an address or access instruction;
• schedule a new attempt;
• arrange hold or pickup;
• clear customs;
• file a claim;
• approve a refund;
• guarantee delivery.

Use it to observe the public record, then use the responsible official or merchant process for action.

Scope, evidence, and limitations

• Primary carrier scope: SwiftX / SwiftX Express in the United States.
• Legal identity used: SWIFTX Inc., based on current official and government sources.
• Cross-border scope: upstream international movement only where it changes interpretation of the later SwiftX record.
• Identifier scope: one observed official SWX plus 18 digits example; no universal format claim.
• Status scope: exact events observed in a current official result plus carefully qualified handling of shipment-specific final-route and exception wording.
• Proof scope: official internal capability to create scans, GPS-linked records, POD photos, and exception media; no universal public-access claim.
• Claims scope: official inquiry route only; no universal recipient eligibility, deadline, liability, or compensation rule.
• Geographic limitation: current official policy directs EU, EEA, and UK users not to use the SwiftX website.
• Last reviewed: July 27, 2026.
• Next scheduled review: October 25, 2026.

11Tracking is not SwiftX, SWIFTX Inc., a marketplace, a seller, a customs authority, a DSP, or a driver. It does not receive, transport, release, reroute, deliver, recover, insure, investigate, or refund a package.