{"id":2448,"date":"2026-08-18T16:03:24","date_gmt":"2026-08-18T08:03:24","guid":{"rendered":"https:\/\/sourcingall.com\/sourcing-basics\/track-shipment-china-to-warehouse\/"},"modified":"2026-08-21T15:52:43","modified_gmt":"2026-08-21T07:52:43","slug":"track-shipment-china-to-warehouse","status":"publish","type":"post","link":"https:\/\/sourcingall.com\/es\/sourcing-basics\/track-shipment-china-to-warehouse\/","title":{"rendered":"How to Track a Shipment From China to Your Warehouse"},"content":{"rendered":"

\u201cWhere is the container?\u201d is usually the wrong first question.<\/p>\n

A shipment can be on a vessel and still be unready for your warehouse. It can arrive at a port while a document, release, broker, appointment, or delivery handoff remains open. A useful tracking process answers a fuller question: what has happened, what is expected next, what evidence supports the status, and who owns the next action?<\/strong><\/p>\n

This article explains an operating workflow for tracking shipments from China to a warehouse. It is written for importers who want fewer surprises, clearer escalation, and a better handoff between supplier, forwarder, carrier, broker, and receiver.<\/p>\n

\n

Information boundary:<\/strong> This is general operational information, not customs, legal, insurance, tax, carrier-liability, claims, or transaction-specific logistics advice. A carrier or third-party tracking page is not a substitute for a broker\u2019s official release confirmation or the applicable government channel. Confirm the requirements and status for each shipment with your carrier\/forwarder, broker, warehouse, and qualified advisers.<\/p>\n<\/blockquote>\n

Track the shipment, not just the vessel<\/h2>\n

A carrier status page can be useful. It is only one stream of information. The arrival date shown on a public page may not tell you whether cargo was handed over correctly, whether the final documents are aligned, whether your broker has the data it needs, or whether the warehouse can receive the delivery.<\/p>\n

Build the tracking plan around the full shipment record.<\/p>\n\n\n\n\n\n\n\n\n\n\n\n
Control area<\/th>\nWhat you need to know<\/th>\nWhy it matters<\/th>\n<\/tr>\n<\/thead>\n
Commercial scope<\/td>\nPO, supplier, buyer\/importer\/consignee, final warehouse, ordered quantity<\/td>\nPrevents tracking the wrong order, entity, or delivery site<\/td>\n<\/tr>\n
Shipment identity<\/td>\nBooking number, carrier\/forwarder reference, B\/L or waybill number, container\/seal number where applicable<\/td>\nGives each team a reliable way to locate the same shipment<\/td>\n<\/tr>\n
Cargo readiness<\/td>\nInspection\/release status, final packing details, pickup\/handoff date<\/td>\nConfirms that tracking started from an authorized physical shipment<\/td>\n<\/tr>\n
Main carriage<\/td>\nService, carrier, vessel\/flight\/truck reference, origin, destination, planned routing<\/td>\nProvides the movement plan that later events are measured against<\/td>\n<\/tr>\n
Document path<\/td>\nCommercial invoice, packing list, B\/L\/waybill workflow, broker\/destination instructions<\/td>\nStops a shipment from moving ahead while documents lag behind<\/td>\n<\/tr>\n
Import and delivery handoff<\/td>\nBroker contacts, destination milestones, appointment, delivery carrier, warehouse receiving window<\/td>\nConnects port\/airport arrival to actual warehouse receipt<\/td>\n<\/tr>\n
Exceptions<\/td>\nDelay, rollover, port change, transshipment change, missing document, damage\/shortage report, appointment issue<\/td>\nMakes sure the right person acts before the issue becomes expensive or disruptive<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n

The best tracking file is simple enough to update daily when the shipment is active. It should be specific enough that a teammate can take over without searching through chat messages.<\/p>\n

Collect the right reference numbers before pickup<\/h2>\n

Do not wait for departure to ask for tracking details. Get the references when the booking is confirmed, then add physical-cargo references at pickup or container loading.<\/p>\n\n\n\n\n\n\n\n\n\n\n\n\n
Reference<\/th>\nWhere it usually comes from<\/th>\nWhat it can help identify<\/th>\nControl note<\/th>\n<\/tr>\n<\/thead>\n
Purchase order<\/td>\nBuyer\u2019s order system<\/td>\nProduct scope and commercial owner<\/td>\nKeep the PO in every tracking record, even when a forwarder uses another reference<\/td>\n<\/tr>\n
Supplier shipment reference<\/td>\nSupplier or origin warehouse<\/td>\nSupplier-side packing, pickup, and handoff discussion<\/td>\nAsk the supplier to state the exact reference used in all updates<\/td>\n<\/tr>\n
Booking number<\/td>\nCarrier or forwarder booking confirmation<\/td>\nA reserved movement\/service and related booking file<\/td>\nU.S. Census defines a booking as a reservation with a carrier for a shipment on a specific voyage, flight, truck, or train. 1<\/a><\/td>\n<\/tr>\n
Bill of lading \/ sea-waybill number<\/td>\nCarrier or forwarder after shipping instructions and issue workflow<\/td>\nA transport-document record and, depending on the setup, carrier\/forwarder tracking<\/td>\nConfirm issuer and document type; do not assume every B\/L reference works in every portal<\/td>\n<\/tr>\n
Container number<\/td>\nCarrier\/forwarder\/container record for containerized cargo<\/td>\nA specific piece of equipment and its movement events<\/td>\nRecord container number and seal information only from controlled sources<\/td>\n<\/tr>\n
Master\/house document reference<\/td>\nCarrier and\/or forwarder<\/td>\nClarifies the carrier-level and forwarder-level document records in a multi-party arrangement<\/td>\nAsk the forwarder which reference should be used for each tracking, broker, and release step<\/td>\n<\/tr>\n
Entry number \/ filer information<\/td>\nCustoms broker and applicable import process<\/td>\nImport-entry status in relevant government or broker systems<\/td>\nTreat as controlled information and do not circulate it more widely than necessary<\/td>\n<\/tr>\n
Delivery-order \/ appointment \/ last-mile reference<\/td>\nDestination carrier, forwarder, drayage provider, warehouse<\/td>\nFinal delivery planning and receipt<\/td>\nAdd these before arrival, not after the cargo is sitting at the terminal<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n

Store the references together with a source, owner, and date checked. A tracking number without its source is hard to trust when two documents conflict.<\/p>\n

Use a tracking register that records evidence, not just dates<\/h2>\n

A shared spreadsheet, transport-management system, or order platform can work. The structure matters more than the software.<\/p>\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
Campo<\/th>\nExample use<\/th>\n<\/tr>\n<\/thead>\n
Shipment ID<\/td>\nInternal ID linking PO, supplier, booking, cargo, and delivery records<\/td>\n<\/tr>\n
PO \/ SKU group<\/td>\nConnects movement to the goods that the warehouse expects<\/td>\n<\/tr>\n
Supplier \/ origin<\/td>\nIdentifies the party handing cargo into the logistics flow<\/td>\n<\/tr>\n
Forwarder \/ carrier<\/td>\nShows who owns the next update and escalation path<\/td>\n<\/tr>\n
Key references<\/td>\nBooking, house\/master document, container, entry, delivery\/appointment references as applicable<\/td>\n<\/tr>\n
Planned route<\/td>\nOrigin, load point, transshipment points, discharge point, delivery point<\/td>\n<\/tr>\n
Latest milestone<\/td>\n\u201cOrigin pickup confirmed,\u201d \u201cloaded,\u201d \u201cdeparted,\u201d \u201carrived,\u201d or another normalized event<\/td>\n<\/tr>\n
Event source and timestamp<\/td>\nCarrier page, forwarder email, terminal notice, broker confirmation, warehouse appointment system; include when checked<\/td>\n<\/tr>\n
Current ETA \/ delivery expectation<\/td>\nPlanning estimate with source\/time, not a guarantee<\/td>\n<\/tr>\n
Next action<\/td>\nThe one action needed to keep the shipment moving<\/td>\n<\/tr>\n
Action owner and due date<\/td>\nPerson\/team that must act and the escalation deadline<\/td>\n<\/tr>\n
Exception code<\/td>\nDelay, route change, document mismatch, holds question, appointment risk, receiving issue, damage\/shortage report<\/td>\n<\/tr>\n
Evidence link<\/td>\nBooking, document version, notice, photo, proof of delivery, warehouse receipt, or message record<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n

The record becomes useful when it shows both the latest update and the next decision. \u201cETA changed\u201d is not enough. Write what changed, where the update came from, who is affected, and what action is due.<\/p>\n

Normalize the milestones your team watches<\/h2>\n

Carrier, forwarder, terminal, broker, drayage, and warehouse systems may use different labels. Create one internal set of milestones so that your team does not argue over vocabulary while a deadline approaches.<\/p>\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
Internal milestone<\/th>\nPossible evidence<\/th>\nBuyer\u2019s control question<\/th>\n<\/tr>\n<\/thead>\n
Cargo ready \/ released<\/td>\nSupplier release, inspection result, final packout<\/td>\nIs the authorized quantity packed and ready for the booked handoff?<\/td>\n<\/tr>\n
Pickup \/ origin handoff<\/td>\nWarehouse receipt, pickup confirmation, handoff record<\/td>\nDid the booked provider receive the correct cargo and count?<\/td>\n<\/tr>\n
Booking confirmed<\/td>\nCarrier\/forwarder booking confirmation<\/td>\nDoes the service, equipment, route, and cutoff still fit the plan?<\/td>\n<\/tr>\n
Loaded \/ departed<\/td>\nCarrier or forwarder event; shipping document event as applicable<\/td>\nHas main carriage started, and are related documents following the agreed workflow?<\/td>\n<\/tr>\n
Transshipment \/ route event<\/td>\nCarrier\/forwarder status<\/td>\nHas routing, vessel\/flight, or expected timing changed? What downstream plan needs updating?<\/td>\n<\/tr>\n
Arrival at port\/airport<\/td>\nCarrier\/terminal\/forwarder status<\/td>\nWhat are the next broker, release, appointment, and pickup prerequisites?<\/td>\n<\/tr>\n
Import-process readiness<\/td>\nBroker confirmation and applicable official channel<\/td>\nHas the broker received accurate documents\/data, and is there any request for action?<\/td>\n<\/tr>\n
Cargo available \/ delivery release step<\/td>\nRelevant provider\/broker confirmation<\/td>\nConfirm actual procedure and authority; do not infer official release from a general tracking status<\/td>\n<\/tr>\n
Delivery appointment<\/td>\nWarehouse\/destination carrier record<\/td>\nIs the warehouse ready, with required slot, equipment, unloading instructions, and contact?<\/td>\n<\/tr>\n
Out for delivery<\/td>\nDrayage\/last-mile update<\/td>\nIs the receiving team prepared for the specified day\/window?<\/td>\n<\/tr>\n
Delivered \/ received<\/td>\nProof of delivery and warehouse receiving record<\/td>\nWas the expected package count\/condition received, and have exceptions been logged?<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n

MSC\u2019s public tracking view includes fields such as container\/B\/L reference, origin, port of load, port of discharge, destination, transshipment, container event date\/location\/description, vessel\/voyage, and ETD\/ETA. 2<\/a> That is a useful example of carrier visibility. It does not mean every carrier, mode, or booking will display the same information.<\/p>\n

Separate four kinds of status<\/h2>\n

A common problem is treating every update as the same kind of truth. They are not.<\/p>\n\n\n\n\n\n\n\n\n
Status type<\/th>\nTypical source<\/th>\nWhat it tells you<\/th>\nWhat it does not tell you by itself<\/th>\n<\/tr>\n<\/thead>\n
Physical movement status<\/td>\nCarrier, terminal, AIS\/event feed, forwarder<\/td>\nA reported equipment, vessel, flight, truck, or cargo event<\/td>\nWhether the commercial documents, broker handoff, and warehouse delivery are ready<\/td>\n<\/tr>\n
Schedule\/ETA status<\/td>\nCarrier schedule, forwarder, delivery provider<\/td>\nA current planning estimate<\/td>\nA guaranteed date or actual availability for pickup\/delivery<\/td>\n<\/tr>\n
Document status<\/td>\nCarrier\/forwarder documentation team, supplier, buyer document control<\/td>\nWhether a document draft, final copy, original, waybill, or release process is at a stated stage<\/td>\nWhether import obligations, payment, title, or legal entitlement are settled<\/td>\n<\/tr>\n
Import\/release status<\/td>\nBroker and appropriate official\/government channel<\/td>\nThe status relevant to the applicable entry\/release workflow<\/td>\nA substitute for physical delivery, warehouse appointment, or receiving confirmation<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n

The Consumer Product Safety Commission makes the distinction clearly for its own import tool: it can show shipment status with an entry number and filer code, but its display is no<\/strong> an official CPSC or U.S. Customs and Border Protection release. It directs users to their broker or ABI messaging for official release information. 3<\/a> Use the same discipline elsewhere: ask the responsible source what its status actually represents.<\/p>\n

Set a rhythm for updates and escalation<\/h2>\n

A shipment does not need the same level of attention every day. Increase the cadence around handoffs, cutoffs, departures, arrivals, document deadlines, and delivery.<\/p>\n\n\n\n\n\n\n\n\n\n\n
Shipment stage<\/th>\nSuggested routine<\/th>\nEscalate when<\/th>\n<\/tr>\n<\/thead>\n
Before origin handoff<\/td>\nConfirm booking, cargo-ready plan, references, final packing, and contact list<\/td>\nCargo is not ready for the planned cutoff, details differ, or key parties are not assigned<\/td>\n<\/tr>\n
Pickup through loading<\/td>\nConfirm physical handoff, equipment\/packing facts, and shipping instructions<\/td>\nHandoff quantity\/condition differs, pickup is missed, or document facts are not controlled<\/td>\n<\/tr>\n
In transit<\/td>\nCheck at the agreed cadence and after meaningful carrier\/forwarder notices<\/td>\nETA, route, service, transshipment, or vessel\/flight changes affect inventory, appointment, or customer commitments<\/td>\n<\/tr>\n
Approaching arrival<\/td>\nCheck daily or as agreed; verify documents and broker\/warehouse readiness<\/td>\nBroker needs information, destination requirements remain open, or warehouse\/last-mile planning is not ready<\/td>\n<\/tr>\n
Arrival through delivery<\/td>\nTrack the applicable release, appointment, pickup, and delivery steps through the responsible parties<\/td>\nA required document, confirmation, appointment, equipment, or contact is missing or timing is at risk<\/td>\n<\/tr>\n
Receiving<\/td>\nMatch proof of delivery and warehouse count\/condition records to the shipment<\/td>\nCount, condition, seal, package, or receiving data differs from expectation<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n

Set internal escalation thresholds in advance. For example, the owner can flag a changed ETA when it threatens a production plan or warehouse appointment, while document and release questions go directly to the relevant forwarder\/carrier, broker, or qualified adviser. Do not wait until a generic \u201cdelayed\u201d label appears.<\/p>\n

Make ETA useful without pretending it is certain<\/h2>\n

An ETA can change due to origin readiness, schedule changes, transshipment, congestion, weather, equipment, terminal operations, documentation, destination handoff, and other events. A buyer needs an ETA for planning, but should not turn it into an unqualified promise to sales, operations, or customers.<\/p>\n\n\n\n\n\n\n\n\n\n\n
ETA record field<\/th>\nBetter practice<\/th>\n<\/tr>\n<\/thead>\n
Date\/time<\/td>\nRecord the exact date\/time shown or received, including timezone when available<\/td>\n<\/tr>\n
Source<\/td>\nName carrier, forwarder, provider, system, or person\u2014not \u201clatest update\u201d<\/td>\n<\/tr>\n
Scope<\/td>\nLabel whether the estimate is port arrival, terminal availability, delivery appointment, or warehouse delivery<\/td>\n<\/tr>\n
Confidence\/action note<\/td>\nState the assumption and the downstream task: \u201cwarehouse hold until appointment is confirmed,\u201d not \u201cdelivery guaranteed\u201d<\/td>\n<\/tr>\n
Previous estimate<\/td>\nRetain the prior version to identify what changed and who needs notification<\/td>\n<\/tr>\n
Owner<\/td>\nAssign the person responsible for the next verification or escalation<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n

MSC says its digital platform can be used to check vessel schedules, submit shipping instructions, manage documentation, and track a specific container. 4<\/a> That supports the practical approach of using the carrier\/forwarder system as one source, then joining it to broker and warehouse evidence.<\/p>\n

Confirm the handoffs the carrier page cannot finish<\/h2>\n

The shipment is not complete when the main carrier reports arrival. Use a destination checklist that crosses organizational boundaries.<\/p>\n\n\n\n\n\n\n\n\n\n\n
Handoff<\/th>\nOwner to confirm<\/th>\nWhat good confirmation looks like<\/th>\n<\/tr>\n<\/thead>\n
Broker document handoff<\/td>\nBuyer\/importer + broker<\/td>\nBroker acknowledges the final controlled document set and identifies any open question<\/td>\n<\/tr>\n
Import-process status<\/td>\nBroker + applicable official channel<\/td>\nA status confirmation from the responsible source, with actions\/conditions clearly recorded<\/td>\n<\/tr>\n
Carrier\/terminal next step<\/td>\nForwarder\/carrier\/agent<\/td>\nThe team knows what condition, release, pickup, or appointment process applies to this shipment<\/td>\n<\/tr>\n
Delivery provider<\/td>\nForwarder\/drayage\/last-mile provider<\/td>\nPickup\/delivery plan, equipment needs, contact, and timing are confirmed<\/td>\n<\/tr>\n
Warehouse appointment<\/td>\nWarehouse\/receiver<\/td>\nDate\/window, unload capability, equipment, labels, and receiving contact are accepted<\/td>\n<\/tr>\n
Delivery and receiving<\/td>\nDelivery provider + warehouse<\/td>\nProof of delivery plus warehouse count\/condition\/exception evidence is in the shipment file<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n

The commercial invoice and packing list should travel with this process, not in a separate email thread. Use Commercial Invoice and Packing List: What Importers Need to Check<\/a> for a document comparison routine, and What Is a Bill of Lading and Why Does It Matter?<\/a> for document-type and release-control questions.<\/p>\n

Turn a delay notice into an action record<\/h2>\n

A delay notice becomes manageable when the buyer turns it into specific impacts and actions.<\/p>\n\n\n\n\n\n\n\n\n\n\n\n
Step<\/th>\nAcci\u00f3n<\/th>\n<\/tr>\n<\/thead>\n
Capture the update<\/td>\nSave source, time, reference, stated event, new estimate, and any reason supplied by the provider<\/td>\n<\/tr>\n
Confirm scope<\/td>\nIdentify whether the change affects one container, booking, document, transshipment, delivery leg, or multiple orders<\/td>\n<\/tr>\n
Check downstream dependencies<\/td>\nReview broker process, warehouse appointment, inventory plan, production schedule, customer promise, and delivery provider availability<\/td>\n<\/tr>\n
Assign owners<\/td>\nGive one person responsibility for provider follow-up and one for each affected business handoff<\/td>\n<\/tr>\n
Set a next-check time<\/td>\nChoose an evidence-based check time rather than repeatedly asking for \u201cany update?\u201d<\/td>\n<\/tr>\n
Communicate a bounded update<\/td>\nState facts, source, open questions, next action, and next update time; avoid presenting an estimate as a guarantee<\/td>\n<\/tr>\n
Preserve the record<\/td>\nKeep the notice, amended booking\/schedule, communications, and any changed appointment\/delivery plan under the shipment ID<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n

For a full exception workflow, see What to Do When a Shipment Is Delayed or Lost<\/a> once that guidance is available in the site library.<\/p>\n

A weekly shipment-tracking dashboard for small teams<\/h2>\n

If you track several shipments, do not review them as a long list of ETAs. Group them by next required action.<\/p>\n\n\n\n\n\n\n\n\n\n\n
Dashboard view<\/th>\nQuestion it answers<\/th>\n<\/tr>\n<\/thead>\n
Needs origin action<\/td>\nWhich shipments could miss a cargo-ready, pickup, loading, or document deadline?<\/td>\n<\/tr>\n
In transit, no exception<\/td>\nWhich movements are on the expected plan and need only scheduled monitoring?<\/td>\n<\/tr>\n
Changed ETA\/route<\/td>\nWhich shipments now affect inventory, customer commitments, destination planning, or appointment windows?<\/td>\n<\/tr>\n
Destination action due<\/td>\nWhich shipments need broker, release, delivery, or warehouse coordination this week?<\/td>\n<\/tr>\n
Receiving\/exception open<\/td>\nWhich deliveries need count, condition, shortage, damage, or evidence follow-up?<\/td>\n<\/tr>\n
Closed<\/td>\nWhich shipment files contain final delivery\/receiving evidence and documented exceptions, if any?<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n

A team can use this dashboard in a short weekly meeting. The discussion should end with owners and due dates, not a vague agreement to \u201ckeep an eye on it.\u201d<\/p>\n

Shipment-tracking checklist<\/h2>\n

Before a shipment leaves China, make sure you have the PO, shipment ID, supplier\/forwarder\/carrier contacts, booking reference, expected document path, destination\/broker\/warehouse contacts, and a plan for physical handoff evidence. During transit, record the latest carrier or forwarder status with source and timestamp, compare it with the actual next business handoff, and escalate material changes through named owners. Before delivery, confirm broker, provider, warehouse, and appointment steps through the responsible parties. At receiving, store proof of delivery and warehouse count\/condition records with any exception evidence.<\/p>\n

Tracking works when it connects transport events to the people who must act. A map pin or vessel name can be useful. A controlled record of movement, documents, release, delivery, and receipt is far more useful.<\/p>\n

Referencias<\/h2>\n
    \n
  1. U.S. Census Bureau, International Trade Definitions<\/em><\/a><\/li>\n
  2. MSC, Tracking<\/em><\/a><\/li>\n
  3. U.S. Consumer Product Safety Commission, Import Shipment Tracking Tool<\/em><\/a><\/li>\n
  4. MSC, eBusiness<\/em><\/a><\/li>\n<\/ol>","protected":false},"excerpt":{"rendered":"

    \u201cWhere is the container?\u201d is usually the wrong first question. A shipment can be on a vessel and still be […]<\/p>","protected":false},"author":1,"featured_media":0,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"rank_math_internal_links_processed":["1"],"rank_math_title":["How to Track a Shipment From China to Your Warehouse"],"rank_math_description":["Build a practical shipment-tracking workflow from China to your warehouse: use the right references, watch key milestones, verify handoffs, and escalate early."],"rank_math_focus_keyword":["track shipment from China"],"rank_math_rich_snippet":["article"],"_rank_math_rich_snippet":["article"],"rank_math_schema_Article":["a:2:{s:5:\"@type\";s:7:\"Article\";s:8:\"headline\";s:52:\"How to Track a Shipment From China to Your Warehouse\";}"],"_rank_math_schema_Article":["a:2:{s:5:\"@type\";s:7:\"Article\";s:8:\"headline\";s:52:\"How to Track a Shipment From China to Your Warehouse\";}"],"_uag_page_assets":["a:9:{s:3:\"css\";s:263:\".uag-blocks-common-selector{z-index:var(--z-index-desktop) !important}@media (max-width: 976px){.uag-blocks-common-selector{z-index:var(--z-index-tablet) !important}}@media (max-width: 767px){.uag-blocks-common-selector{z-index:var(--z-index-mobile) !important}}\n\";s:2:\"js\";s:0:\"\";s:18:\"current_block_list\";a:15:{i:0;s:11:\"core\/search\";i:1;s:10:\"core\/group\";i:2;s:12:\"core\/heading\";i:3;s:17:\"core\/latest-posts\";i:4;s:20:\"core\/latest-comments\";i:5;s:13:\"core\/archives\";i:6;s:15:\"core\/categories\";i:8;s:25:\"greenshift-blocks\/heading\";i:9;s:22:\"greenshift-blocks\/text\";i:10;s:14:\"core\/paragraph\";i:12;s:18:\"core\/legacy-widget\";i:13;s:17:\"core\/social-links\";i:15;s:16:\"core\/social-link\";i:16;s:21:\"trp\/language-switcher\";i:17;s:9:\"core\/html\";}s:8:\"uag_flag\";b:0;s:11:\"uag_version\";s:10:\"1787298764\";s:6:\"gfonts\";a:0:{}s:10:\"gfonts_url\";s:0:\"\";s:12:\"gfonts_files\";a:0:{}s:14:\"uag_faq_layout\";b:0;}"],"_uag_css_file_name":["uag-css-2448.css"]},"categories":[32],"tags":[],"class_list":["post-2448","post","type-post","status-publish","format-standard","hentry","category-sourcing-basics"],"uagb_featured_image_src":{"full":false,"thumbnail":false,"medium":false,"medium_large":false,"large":false,"1536x1536":false,"2048x2048":false,"trp-custom-language-flag":false},"uagb_author_info":{"display_name":"admin","author_link":"https:\/\/sourcingall.com\/es\/author\/admin\/"},"uagb_comment_info":0,"uagb_excerpt":"\u201cWhere is the container?\u201d is usually the wrong first question. A shipment can be on a vessel and still be […]","_links":{"self":[{"href":"https:\/\/sourcingall.com\/es\/wp-json\/wp\/v2\/posts\/2448","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/sourcingall.com\/es\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/sourcingall.com\/es\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/sourcingall.com\/es\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/sourcingall.com\/es\/wp-json\/wp\/v2\/comments?post=2448"}],"version-history":[{"count":1,"href":"https:\/\/sourcingall.com\/es\/wp-json\/wp\/v2\/posts\/2448\/revisions"}],"predecessor-version":[{"id":2635,"href":"https:\/\/sourcingall.com\/es\/wp-json\/wp\/v2\/posts\/2448\/revisions\/2635"}],"wp:attachment":[{"href":"https:\/\/sourcingall.com\/es\/wp-json\/wp\/v2\/media?parent=2448"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/sourcingall.com\/es\/wp-json\/wp\/v2\/categories?post=2448"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/sourcingall.com\/es\/wp-json\/wp\/v2\/tags?post=2448"}],"curies":[{"name":"gracias","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}