Amazon Swiship Tracking

Amazon Swiship at a glance

• What Swiship is: an Amazon MCF tracking surface for some off-Amazon orders.
• What it is not: a standalone delivery company, seller, marketplace, refund desk, or returns service.
• Possible tracking identifiers: an Amazon Fulfillment Tracking Number (AFTN), an Amazon Logistics TBA number, or another carrier's package-level tracking number.
• Possible physical carriers: Amazon Logistics or a third-party carrier selected by MCF.
• What an AFTN proves: Amazon created an MCF tracking record; it does not by itself prove pickup or movement.
• What Carrier Assigned proves: a carrier and carrier tracking number were selected in the documented workflow; it does not prove physical carrier possession.
• What Delivered proves: a delivery outcome was recorded; it does not automatically prove that the named shopper personally received the package.
• Best commercial contact: the seller or store shown on the original receipt.

What to enter in the tracking form

Enter one package-level identifier at a time. The safest source is the merchant's shipment email or order page.

Use a number explicitly described as:

• AFTN or Amazon Fulfillment Tracking Number;
• tracking number;
• carrier tracking number;
• Amazon Logistics tracking number, often beginning with TBA, when the merchant confirms that it belongs to this MCF package;
• a third-party carrier number, such as a UPS, postal, or parcel-carrier identifier, when that carrier is named for the shipment.

Do not enter:

• a store order number unless the merchant specifically labels it as trackable;
• an Amazon.com retail order number;
• an MCF fulfillment-order ID intended for Seller Central or an API;
• a product SKU, return authorization, invoice number, or payment reference;
• several package numbers in one field.

A multi-item order can be split into separate packages. Each package may have a different tracking number, event history, delivery date, or carrier. One Delivered event should not be treated as proof that every item in the commercial order arrived.

What Amazon Swiship actually is

Swiship sits between an outside merchant's order and the carrier event history that Amazon MCF makes available.

A common order path is:

Customer buys from an outside store
        ↓
Merchant uses Amazon Multi-Channel Fulfillment
        ↓
Amazon picks and packs inventory from its fulfillment network
        ↓
MCF creates shipment and tracking records
        ↓
Amazon Logistics or another carrier transports the package
        ↓
Swiship presents available fulfillment and carrier events

The Amazon branding can be confusing because the purchase may have been made through a brand website, Shopify store, social-commerce channel, or another marketplace. In that situation, Amazon may be the merchant's fulfillment provider without being the seller of the item.

Swiship therefore does not establish that:

• the purchase was made on Amazon.com;
• Amazon is the merchant of record;
• Amazon retail customer service can refund or replace the item;
• Amazon Logistics is the physical carrier;
• the shipment will use Amazon-branded packaging;
• the Swiship page can change the address, cancel the order, authorize a return, or open a shopper claim.

Why a non-Amazon store sent an Amazon tracking link

Amazon MCF lets a merchant use Amazon's fulfillment network for orders placed outside Amazon's retail marketplace. The merchant can store inventory in Amazon facilities and ask Amazon to pick, pack, and ship an order from another sales channel.

That creates two separate relationships:

1. The shopper and seller: the store accepted payment, owns the order, and controls refunds, replacements, returns, and customer communication.
2. The merchant and Amazon MCF: the merchant or account holder buys fulfillment services and can use Amazon-side order support or reimbursement processes when eligible.

The recipient usually sees only part of the second relationship. Swiship makes selected tracking data visible, but it does not transfer the merchant's MCF account rights to the shopper.

AFTN, carrier tracking numbers, and TBA numbers

Several identifiers can appear during one MCF shipment. They are not interchangeable in every context.

What an AFTN means

AFTN means Amazon Fulfillment Tracking Number. Amazon currently documents AFTN as a way for supported MCF integrations to receive a shopper-facing tracking identifier before a final carrier tracking number is available.

An AFTN can appear within minutes after order creation. The carrier field may still be UNASSIGNED at that point.

The correct evidence boundary is:

AFTN exists
=
Amazon created an MCF fulfillment tracking record

Amazon's current public AFTN guidance is most explicit in a TikTok Shop MCF integration and currently describes a limitation for multi-item orders in that workflow. That documentation should not be converted into either a universal guarantee or a permanent prohibition across every MCF channel. AFTN availability can depend on the merchant integration and the order structure.

What a carrier tracking number means

The carrier tracking number belongs to the selected physical carrier. Depending on the route, it may be:

• an Amazon Logistics TBA identifier;
• a UPS 1Z number;
• a postal tracking number;
• another carrier-specific package number.

Amazon's official technical model includes a carrier code, carrier tracking number, and carrier URL or contact fields when available. An official MCF example pairs a UPS tracking number with a Swiship customer link, confirming that Swiship can present a shipment handled by another carrier.

Which number should you use?

Use this order:

1. Open the seller's shipping email or order page.
2. Copy the package-level number labeled AFTN, tracking number, or carrier tracking number.
3. If both AFTN and carrier number are shown, use either supported identifier, then compare the carrier's official tracker when the carrier is named.
4. If the order was split, track each package separately.
5. If none of the supplied numbers works, ask the seller to confirm the current package-level tracking number and underlying carrier.

Do not infer that a number is valid for Swiship merely because it begins with TBA, contains the word Amazon, or appeared in an unrelated Amazon workflow.

What the early Swiship and AFTN events prove

The early MCF events are especially important because they separate fulfillment preparation from carrier possession.

Order Preparing

Amazon describes this as the stage where inventory is being picked and the order is being packed. It is a fulfillment event, not a carrier possession event.

If Order Preparing remains unchanged, compare it with the seller's stated dispatch promise. Do not assume the package is lost merely because no carrier has been assigned yet.

Carrier Assigned

Amazon's documented AFTN flow describes this as the point where a shipping label is created, a carrier is selected, and the carrier tracking number becomes available.

It is stronger than an unassigned AFTN, but it still does not prove that the carrier physically collected the package.

The safest interpretation is:

Amazon selected the planned carrier and created the carrier shipment record. Look for Shipped, a pickup event, an acceptance event, or a carrier facility scan for stronger evidence of physical movement.

Shipped

In the documented AFTN workflow, Shipped means the package left the Amazon fulfillment center.

That is stronger departure evidence, but it does not establish that:

• the final-mile carrier already has the package;
• no consolidator or intermediate carrier is involved;
• the package will move continuously without a scan gap;
• the estimated delivery date is guaranteed.

Who is actually delivering the package?

Swiship is a visibility layer. The underlying carrier controls the physical route.

When Amazon Logistics is assigned

A shipment handled by Amazon Logistics may use a TBA tracking identifier. Eligible deliveries can also expose Amazon-specific evidence such as a delivery photograph, drop-point location, or information about a handoff to a neighbor, reception desk, or mail room.

Those features depend on the shipment, delivery type, market, and current eligibility. They must not be assumed for every TBA package or every Swiship record.

When a third-party carrier is assigned

The package may use UPS, a postal operator, or another parcel carrier. In that case:

• Swiship may still show the event history;
• the carrier name and carrier tracking number may appear;
• the carrier's own official tracker may contain more operational detail;
• delivery instructions, pickup actions, claims, or proof may follow that carrier's rules;
• Amazon Logistics photo and drop-point features may not apply.

When the carrier changes or a handoff appears

Amazon's official event model includes an event for receipt from a prior carrier. This supports genuine inter-carrier handoffs, but does not mean that every MCF shipment changes carriers.

When a later event names a different carrier:

1. read the exact event rather than relying on the original carrier field alone;
2. use the latest attributable carrier tracking number for current operational detail;
3. distinguish a carrier assignment from a recorded physical handoff;
4. keep the seller involved if the package becomes disputed.

How to read common Swiship statuses

Swiship can present normalized fulfillment and carrier statuses. The exact event text, carrier, timestamp, and location matter more than the broad parent label.

IN_TRANSIT

IN_TRANSIT means the shipment is within a recorded transportation or processing flow. It does not tell you by itself whether the package is on a vehicle, at a carrier facility, crossing a border, waiting between scans, or moving through an intermediate carrier.

Read the latest detailed event. Arrival, departure, customs, and handoff events describe different stages.

OUT_FOR_DELIVERY

OUT_FOR_DELIVERY records an active final-delivery stage. It is not a guarantee of successful delivery that day.

The next event may be:

• DELIVERED;
• DELIVERY_ATTEMPTED;
• DELAYED;
• CUSTOMER_ACTION;
• AVAILABLE_FOR_PICKUP;
• UNDELIVERABLE;
• a return event.

DELIVERY_ATTEMPTED

A delivery attempt was recorded, but the exact reason controls what happens next. Possible branches include another attempt, pickup, address or access action, carrier contact, or return processing.

Do not assume that every carrier uses the same number of attempts, reattempt timing, notice method, or pickup holding period.

AVAILABLE_FOR_PICKUP

Pickup readiness was recorded. The location, required identification, authorization rules, access hours, and holding period belong to the underlying carrier or pickup location.

Do not travel to a facility until the exact event confirms the pickup site and readiness.

DELAYED

The route or commitment is delayed. The status does not identify the cause by itself. Read the detailed event for weather, network, customs, access, damage, address, or other dependencies.

CUSTOMER_ACTION

The shipment requires recipient or merchant action. The detailed event should identify whether the issue concerns contact, address information, pickup, customs, appointment, or another dependency.

Never submit payment or identity data through an unverified message merely because it mentions the shipment.

UNDELIVERABLE

The fulfillment or carrier system recorded that delivery could not be completed. This does not by itself determine whether the seller will replace, refund, reship, or wait for a return.

RETURNING and RETURNED

RETURNING indicates reverse movement. RETURNED indicates that return completion was recorded in the relevant fulfillment or carrier workflow.

Neither status automatically proves:

• merchant inspection;
• refund approval;
• refund issuance;
• payment settlement;
• closure of a marketplace dispute.

UNKNOWN

UNKNOWN means the current normalized status cannot safely classify the event. It should not be rewritten as loss, delay, or fraud without the underlying event text.

Detailed event families you may see

Amazon's current MCF technical model includes detailed events covering:

• carrier notification and physical pickup;
• arrival and departure scans;
• destination-country arrival;
• customs processing and completion;
• movement to a pickup point;
• out-for-delivery and delivery attempts;
• delivery appointments;
• pickup readiness and locker events;
• carrier-to-carrier receipt;
• damage, loss, refusal, address problems, and weather delay;
• return requests, return movement, fulfillment-center return receipt, and refund events.

These event families show that Swiship can expose more than a simple five-stage timeline. They do not guarantee that every shipment, carrier, market, or public interface will show every technical field or event code.

Delivery estimates and delivery windows

An MCF shipment can contain several time concepts:

• the merchant's checkout promise;
• the latest ship date in the fulfillment workflow;
• the latest delivery date;
• a carrier-estimated delivery date;
• a destination-station delivery window;
• a completed delivery event.

These are not interchangeable.

A delivery window may become available only after the package reaches a destination station. Its absence early in the route does not by itself indicate a problem.

Amazon advertises particular MCF service speeds in certain markets and service contexts, but those values should not be treated as universal Swiship delivery promises. Actual timing can depend on inventory location, service selection, destination, carrier, market, weather, customs, access, and operational exceptions.

What a `Delivered` status proves

A Delivered status confirms that the underlying carrier or MCF visibility system recorded delivery completion.

It does not automatically prove:

• that the named shopper personally received the package;
• that the correct physical address was used;
• that a named neighbor, receptionist, or other person was authorized;
• that the package remained secure after placement;
• that a photograph exists;
• that a photograph depicts the correct parcel and location;
• that theft, misdelivery, or scanning error is impossible.

The strongest available interpretation uses the complete evidence set: exact delivery event, timestamp, carrier, drop-point classification, eligible photo, recipient detail, package identity, and the user's observation.

Delivery photos and drop-point details

Amazon announced photo on delivery and drop-point logging for eligible Amazon Logistics MCF deliveries in North America and the European Union. Eligible evidence may be available through Swiship, Seller Central, or the Amazon Selling Partner API.

Photo on delivery

A delivery photo can help identify a doorway, porch, reception area, mail room, locker, or another placement point. It remains carrier-recorded evidence rather than independent proof of every disputed fact.

A photo does not automatically prove:

• personal receipt;
• correct address;
• parcel contents;
• continued security after placement;
• absence of a later theft or collection mistake.

Current launch language applies to eligible unattended Amazon Logistics MCF orders. Do not expect a Swiship photo for every package or for a third-party carrier that uses different proof rules.

Drop-point logging

Eligible drop-point details may identify a location or person, including examples such as:

• front door, rear door, or side porch;
• garage or another secure location;
• front desk, reception, or mail room;
• neighbor;
• guard or security desk;
• locker;
• another recorded delivery point.

Amazon also describes recipient or handoff details for eligible attended deliveries, such as a neighbor or receptionist name. Those fields remain operational records. They do not automatically establish authorization or legal sufficiency in every dispute.

Postal-code verification and privacy

The official evidence flow can require verification of the destination postal or ZIP code before showing a photo or recipient detail.

11Tracking does not collect that postal code, unlock private evidence, proxy delivery images, store signatures, or expose recipient names. Open the official Swiship page directly through the seller's verified order record or the official Amazon domain.

Tracking number not found

A rejected or empty Swiship result can have several explanations:

• the seller supplied an order ID instead of a tracking number;
• the AFTN is not active in that merchant integration;
• carrier assignment has not occurred;
• the package-level number has not yet been shared;
• the number was copied incorrectly;
• the order was split and the wrong package number was used;
• the identifier belongs to Amazon retail, Amazon Shipping, an inbound shipment, a removal order, or another Amazon workflow;
• the underlying carrier number should be used on that carrier's official site;
• the regional Swiship link or locale is wrong;
• an older record is no longer available.

Use this sequence:

1. Copy the identifier again from the merchant's current order page or shipping email.
2. Confirm whether it is labeled AFTN, tracking number, or carrier tracking number.
3. Remove accidental spaces or punctuation without changing the identifier itself.
4. Use the official Swiship link supplied by the merchant or the verified official Swiship site.
5. If a carrier is named, try the package-level number on that carrier's official tracker.
6. Ask the seller to confirm the current package number, package count, and physical carrier.

Do not publish the full identifier in a public forum or send it to an unverified support account.

AFTN shows `UNASSIGNED` or no carrier

An AFTN can exist before the carrier is selected. UNASSIGNED does not by itself prove delay, loss, or cancellation.

Compare the record with:

• the seller's dispatch promise;
• the latest ship date shown for the order;
• whether Order Preparing appears;
• whether Carrier Assigned or Shipped appears later;
• whether the order was split or changed during packaging.

If the merchant's stated dispatch window has passed without carrier assignment or departure, contact the seller. The merchant can view account-side MCF order details that are not available to the shopper.

Swiship tracking is not updating

Public tracking is an event history, not continuous GPS. A gap can mean:

• the package remains in fulfillment preparation;
• carrier assignment is pending;
• the carrier has not produced a new public scan;
• events have not synchronized between systems;
• the package is moving between recorded checkpoints;
• a third-party carrier has a separate or richer event stream;
• a delay or exception has not yet been normalized into a broad status.

Do not use a universal “wait 24 or 48 hours” rule. Instead, compare:

• the strongest physical event already recorded;
• the latest estimated date;
• the underlying carrier's official record;
• the seller's dispatch and delivery commitments;
• any action or exception event.

Contact the seller when the promised dispatch or delivery window has passed, the package has no usable identifier, or the event history becomes contradictory.

`Out for Delivery` but not delivered

OUT_FOR_DELIVERY records an active final-delivery operation. Route capacity, access, weather, address issues, security restrictions, an unsuccessful attempt, or another operational event can prevent completion.

Check for a later event such as:

• DELIVERY_ATTEMPTED;
• DELAYED;
• CUSTOMER_ACTION;
• AVAILABLE_FOR_PICKUP;
• UNDELIVERABLE;
• return processing.

The underlying carrier controls route operations. The seller remains responsible for the commercial resolution if the shipment does not arrive.

`Delivered` but the package is missing

Use the complete evidence rather than the parent status alone.

1. Confirm the package. Check whether the order was split and whether the delivered event belongs to the missing item.
2. Read the exact location. Look for front door, reception, mail room, neighbor, locker, secure location, or another drop-point detail.
3. Open eligible evidence only on the official Swiship page. Verify the destination postal or ZIP code directly with Amazon when required.
4. Check the indicated location. Ask household members, reception, building staff, security, or the named neighbor when supported by the record.
5. Preserve evidence. Save the order page, shipment events, delivery date, seller messages, and any eligible photo or recipient detail.
6. Contact the seller or store. Request the appropriate investigation, replacement, or refund under the merchant's process.
7. Use the physical carrier's official reporting path when required. The merchant may also need to use its Amazon MCF account for support or reimbursement.

A photo or named drop point can narrow the search. It does not automatically end a delivery dispute.

Damaged, lost, refused, or undeliverable packages

Amazon's official MCF event model includes damage, loss, refusal, hold, address problem, weather, undeliverable, and return events. These events can establish that a problem was recorded, but they do not automatically determine:

• who may file a carrier claim;
• whether Amazon will reimburse the merchant;
• whether the shopper receives a full refund;
• whether a replacement will be sent;
• which marketplace or payment deadline applies;
• legal responsibility for the outcome.

For an outside-store purchase, contact the seller. The seller owns the commercial resolution and can use the MCF account or underlying-carrier process available to it.

Returns, refunds, and MCF reimbursements

Swiship shows tracking. It does not authorize merchandise returns or issue shopper refunds.

Returns

The seller controls the return decision. Amazon MCF provides account-side return workflows that a merchant may use, including a return mailing label or authorization slip in supported cases. Those are merchant tools, not permission for a shopper to send a parcel directly to an Amazon fulfillment center without seller authorization.

Do not create an address or return label from tracking information alone. Contact the seller for the correct return instructions.

Refunds

The shopper paid the outside merchant. The merchant therefore owns the refund relationship.

A RETURNED or RETURN_RECEIVED_IN_FC event does not prove that the merchant inspected the item, approved a refund, issued payment, or completed settlement.

MCF reimbursements

Amazon may provide an eligible reimbursement process to the merchant or MCF account holder under current service terms. That account-side process is not a direct shopper claim against Swiship.

Seller reimbursement rules and shopper dispute deadlines are different systems. A seller should review current MCF rules promptly, while the shopper should preserve applicable store, marketplace, card, or consumer-protection deadlines.

Who should you contact?

If the item was bought from another store, Amazon retail support may not have the transaction needed to refund or replace it. Start with the seller shown on the original receipt.

Swiship, Amazon Logistics, Amazon Shipping, and Amazon retail tracking

These names describe different objects.

Swiship is not Amazon Shipping

Amazon Shipping has its own tracking and support experience. A package tracked through Amazon Shipping should not be classified as Swiship merely because both services use Amazon branding.

Swiship is not the same as Amazon Logistics

Amazon Logistics can be the physical carrier shown inside Swiship, but Swiship can also present a third-party carrier. Treat the carrier field and package-level tracking number as the operational evidence.

Swiship is not Amazon retail order tracking

An Amazon retail order belongs to the buyer's Amazon account and retail support system. An outside merchant's MCF order belongs to the seller's customer relationship even when Amazon performs fulfillment.

Safety and privacy

Use the official tracking link from the merchant's order record or a verified Amazon/Swiship domain.

Be cautious when a message:

• asks for an unexpected redelivery or customs fee;
• uses a lookalike domain;
• requests card details, passwords, one-time codes, or identity documents;
• asks you to reply with the full tracking number and postal code;
• creates urgency around an address correction without a matching official event;
• claims that Swiship can issue a refund after a small payment.

A real tracking number can be copied into a fraudulent message. The number alone does not authenticate the sender.

Do not post publicly:

• the full AFTN, TBA, or carrier tracking number;
• destination postal or ZIP code;
• delivery photograph;
• recipient or neighbor name;
• signature;
• home address, phone number, or access code;
• invoice or payment information.

11Tracking does not need these private details to explain the public event history.

Using USTracking with an Amazon MCF shipment

USTracking can help organize supported public tracking events and make later updates easier to review. It cannot create an AFTN, assign a carrier, unlock a Swiship delivery photo, verify a destination postal code, contact Amazon or the driver, change an address, authorize a return, issue a refund, open an MCF reimbursement request, or recover a package.

Use the official Swiship page and the underlying carrier for current shipment evidence. Use the seller for the commercial order decision.

Frequently asked questions

Is Swiship a carrier?

No. Amazon's official Swiship interface identifies it as a tracking tool and states that it is not the delivery carrier. The physical carrier may be Amazon Logistics or another carrier selected for the MCF shipment.

Why does a purchase from another store use Amazon Swiship?

The store may use Amazon Multi-Channel Fulfillment. Amazon can pick, pack, and ship the merchant's off-Amazon order while the outside store remains the seller and customer-service contact.

What is an AFTN?

AFTN means Amazon Fulfillment Tracking Number. It is an Amazon MCF tracking identifier that can exist before the final carrier tracking number. Its existence confirms an MCF tracking record, not carrier pickup or shipment departure.

Does Carrier Assigned mean the carrier has the package?

Not necessarily. In Amazon's documented AFTN workflow, Carrier Assigned means a carrier was selected and a carrier label/tracking number was created. Look for Shipped, a physical pickup event, an acceptance event, or a carrier facility scan for stronger possession evidence.

Can Swiship track a TBA number?

A TBA number may belong to an Amazon Logistics MCF shipment and may appear in Swiship. However, not every TBA identifier belongs to MCF or is guaranteed to work on Swiship. Use the link and number supplied for the specific merchant order.

Can Swiship track UPS or another carrier?

Yes, when that carrier is assigned to an MCF package and the integration exposes its tracking data. Amazon's official technical example pairs a UPS tracking number with a Swiship customer link. The carrier's own official tracker may provide additional operational detail.

Does every Swiship delivery include a photo?

No. Amazon currently describes photo on delivery for eligible unattended Amazon Logistics MCF orders in specified markets. Third-party carrier deliveries and ineligible shipments may not include a photo.

Does a delivery photo prove that I received the package?

No. A photo is carrier-recorded placement evidence. It can help identify the location but does not automatically prove personal receipt, correct address, package contents, continued security, or absence of misdelivery.

Why is the carrier UNASSIGNED?

An AFTN can be created before MCF selects the physical carrier. Compare the status with the seller's dispatch promise and look for Carrier Assigned or Shipped. Contact the seller if the dispatch window has passed.

Who handles a missing Swiship package?

For an off-Amazon purchase, the seller or store is the primary commercial contact. The underlying carrier may provide route or delivery evidence, while the merchant can use its Amazon MCF account for support or reimbursement when eligible.

Can Amazon customer service refund a Swiship order?

Amazon retail customer service may not own an order placed with another store. Contact the seller shown on the original receipt for refund, replacement, or return decisions.

Is Amazon Shipping the same as Swiship?

No. Amazon Shipping is a separate parcel-carrier service with its own tracking and help experience. Swiship is a multi-carrier tracking portal for some Amazon MCF shipments.

Does Returned mean the seller issued my refund?

No. It records a return outcome in the fulfillment or carrier flow. Merchant inspection, refund approval, payment issuance, and settlement are separate events.

Related package-tracking guides

• What Does “Label Created” Mean? — distinguish shipment data and carrier selection from physical possession.
• Carrier Received Package — identify stronger evidence of physical acceptance.
• How Package Tracking Works — understand event-based tracking and scan gaps.
• Handed to a Local Carrier — interpret a recorded carrier handoff without assuming every shipment changes carriers.
• Out for Delivery — understand the final-route stage and its limitations.
• Delivered — interpret carrier-recorded completion and delivery evidence.
• Tracking Number Not Found — troubleshoot the wrong identifier, inactive record, or wrong tracking system.
• Tracking Not Updating — decide what a silent event history does and does not prove.
• Delivered but Not Received — follow the full evidence-preservation and recovery sequence.
• Who to Contact About a Package — route the issue to the seller, carrier, marketplace, sender, or account holder.

Sources, scope, and review

This page was researched from current official Amazon, Swiship, Amazon MCF, Amazon Selling Partner API, and Amazon Shipping materials accessed on July 27, 2026.

The page covers Swiship as an Amazon MCF tracking portal. It does not provide a universal directory of every Amazon fulfillment program, Amazon Logistics route, Amazon Shipping market, AFTN integration, carrier claim rule, return window, reimbursement deadline, delivery-photo entitlement, or tracking-retention period.

Swiship behavior can vary by market, merchant integration, package structure, underlying carrier, delivery type, and account configuration. Technical API fields describe supported system capabilities; they do not guarantee that each field appears for every package or in every public locale.

The page does not diagnose a live shipment, collect postal codes, retrieve delivery images, act on a merchant's MCF account, authorize a return, or determine legal responsibility.

Last reviewed: July 27, 2026 Next review due: October 27, 2026