About CGSD
CGSD is the carrier identity associated with the supplied company website below. Use the shipment identifier issued by the seller, shipping label, dispatch message, or logistics record to check available events. A tracking result may also identify another carrier responsible for an origin, line-haul, customs, or last-mile stage.
CGSD Overview
Carrier Entity Relationships
| Entity | Entity type |
| CGSD | Canonical carrier identity |
View all details for CGSD
| Relationship to CGSD | CGSD is the carrier name users should select or search when checking a CGSD-linked shipment. |
| Why it matters to tracking | Using the exact carrier identity reduces the risk of interpreting events from an unrelated carrier with a similar name. |
| Official evidence | The supplied company website identifies the relevant web domain. |
|
| 17TRACK | Independent multi-carrier tracking platform |
View all details for 17TRACK
| Relationship to CGSD | 17TRACK can display carrier events made available through its tracking network; 17TRACK does not transport CGSD shipments. |
| Why it matters to tracking | 17TRACK can help users follow multi-carrier shipments and normalize event descriptions in one interface. |
| Official evidence | The 17TRACK tracking platform and API documentation describe multi-carrier tracking functions. |
|
| Seller or shipping merchant | Shipment-data source and commercial counterparty |
View all details for the seller relationship
| Relationship to CGSD | The seller normally supplies the tracking identifier and may have the shipping contract used for the shipment. |
| Why it matters to tracking | The seller can correct an order-to-tracking-number mismatch and may need to open a transport inquiry or commercial refund request. |
| Official evidence | The applicable evidence is the buyer's order record, dispatch notice, and shipping label. |
|
Quick Answer
To track a CGSD package, copy the shipment tracking number from the dispatch notice or order page and enter it on the supplied CGSD website or 17TRACK. If no result appears, first remove accidental spaces, confirm that the value is a tracking number rather than an order number, and ask the seller whether the parcel has received a physical acceptance scan.
Pro Tip: 17TRACK is an independent tracking platform. It cannot transport a parcel, change its address, clear customs, approve a claim, or issue a seller refund.
How to Track CGSD Packages
Track CGSD with the exact shipment identifier shown in the shipping record. Keep the original identifier even if a later event displays a separate partner or last-mile number.
- Open the merchant's order page, dispatch email, shipping label, or receipt.
- Copy the value labelled tracking number, logistics number, waybill number, or shipment number.
- Open the supplied CGSD website and use its available tracking function.
- Alternatively, enter the same identifier on 17TRACK.
- Read the latest event together with its date, location, responsible carrier, and any linked last-mile number.
Which Identifier Should You Use?
| Identifier | How to use it |
| Tracking or waybill number | Use this first for carrier tracking. |
| Order number | Use it with the seller; it may not be accepted by a carrier tracker. |
| Merchant reference | Use it to locate the order and obtain the carrier-issued shipment identifier. |
| Partner or last-mile number | Use it after a tracking event identifies the destination delivery carrier. |
| Delivery notice number | Use it with the carrier or facility named on the physical notice. |
Tracking Statuses and Meanings
CGSD-related event wording can differ by data source and partner. Interpret each event by lifecycle stage, scan location, timestamp, and the carrier currently named in the tracking result.
Status Quick Lookup
| Status | What it means |
| Shipment information received | Electronic shipment data exists, but this event alone does not prove physical acceptance. |
View all details for shipment information received| Lifecycle stage | Pre-shipment |
|---|
| Current responsible party | The seller or shipping party remains responsible for tendering the parcel. |
|---|
| What happens next | A physical acceptance or facility scan should appear after handover. |
|---|
| What you should do | Ask the seller for the handover date if the status persists beyond the promised dispatch window. |
|---|
|
| Accepted or received | A carrier or logistics facility has recorded physical receipt. |
View all details for accepted or received| Lifecycle stage | Accepted |
|---|
| Current responsible party | The carrier or facility named in the event. |
|---|
| What happens next | Sorting, consolidation, or departure processing. |
|---|
| What you should do | Monitor the next facility or departure scan. |
|---|
|
| In transit or departed facility | The parcel is moving between logistics nodes or awaiting its next processing scan. |
View all details for in transit| Lifecycle stage | Line-haul or network transit |
|---|
| Current responsible party | The carrier or transport partner controlling the current leg. |
|---|
| What happens next | Arrival, unloading, sorting, or a partner handoff. |
|---|
| What you should do | Compare the latest scan with the seller's delivery window before escalating. |
|---|
|
| Customs processing | The shipment is undergoing import or export formalities; arrival at customs does not mean release. |
View all details for customs processing| Lifecycle stage | Customs and regulatory review |
|---|
| Current responsible party | Customs, a broker, or the carrier holding the parcel for customs. |
|---|
| What happens next | Release, document request, tax collection, inspection, or return decision. |
|---|
| What you should do | Respond promptly if the carrier, broker, seller, or customs authority requests documents or payment. |
|---|
|
| Handed to delivery partner | A partner is expected to control a later route stage; electronic notice may precede physical handover. |
View all details for carrier handoff| Lifecycle stage | Partner handoff |
|---|
| Current responsible party | The last carrier with a physical receipt scan remains the clearest custodian until the partner records acceptance. |
|---|
| What happens next | The partner receives, sorts, and assigns the parcel to its local network. |
|---|
| What you should do | Track both identifiers and wait for the partner's first physical scan. |
|---|
|
| Out for delivery | The destination delivery unit has assigned the parcel to a delivery route. |
View all details for out for delivery| Lifecycle stage | Final mile |
|---|
| Current responsible party | The named last-mile carrier. |
|---|
| What happens next | Delivery, a pickup instruction, or an exception scan. |
|---|
| What you should do | Keep access clear and monitor messages from the delivery carrier. |
|---|
|
| Delivered | A delivery completion scan was recorded at the stated location or recipient point. |
View all details for delivered| Lifecycle stage | Delivery completed |
|---|
| Current responsible party | The recipient controls the parcel after correct delivery; the delivery carrier investigates disputed scans. |
|---|
| What happens next | No further transport event is expected unless a correction, return, or dispute is recorded. |
|---|
| What you should do | Check the delivery location, household, reception, neighbours, parcel lockers, and proof of delivery before reporting a missing parcel. |
|---|
|
| Delivery exception | Delivery could not proceed because of access, address, recipient, weather, operational, or compliance conditions. |
View all details for a delivery exception| Lifecycle stage | Exception |
|---|
| Current responsible party | The named delivery facility or last-mile carrier. |
|---|
| What happens next | Another attempt, pickup instruction, address review, or return processing. |
|---|
| What you should do | Follow the event instruction and contact the named carrier if action is requested. |
|---|
|
| Return to sender | The parcel has entered a reverse route because delivery or import completion did not occur. |
View all details for return to sender| Lifecycle stage | Return |
|---|
| Current responsible party | The carrier moving the return; the seller handles replacement or refund decisions. |
|---|
| What happens next | Reverse transport and delivery back to the return address. |
|---|
| What you should do | Contact the seller with the return event and avoid assuming that the original parcel can still be redirected. |
|---|
|
Services and Delivery Times
Use the service name and delivery window written in the seller's shipping record. A checkout estimate, carrier service standard, tracking-derived estimate, and guaranteed delivery commitment are different concepts and should not be treated as interchangeable.
Service Comparison
| Service | Best for |
| Service shown on the CGSD-linked shipment record | The route and shipment type purchased by the seller or shipper. |
View all details for the recorded shipment service
| Service type | Use the exact service description printed on the label, manifest, order page, or transport contract. |
| Coverage | Use the origin and destination listed in the shipment record. |
| Tracking level | Depends on scans supplied by each carrier participating in the route. |
| Key size/weight condition | The accepted label and shipping contract govern the shipment's declared weight and dimensions. |
| Included protection/extra service | Use the purchase record to determine any declared value, insurance, signature, or other paid option. |
| Main limitation | Tracking visibility does not by itself establish insurance, a guaranteed date, or entitlement to compensation. |
|
Delivery Time
| Service | Published delivery standard |
| CGSD-linked shipment | Use the service-specific window in the shipping contract, checkout record, or dispatch notice. |
View all delivery-time details for a CGSD-linked shipment
| Business or calendar days | Apply the day-count definition in the purchased service terms. |
| Guarantee status | Treat a date as guaranteed only when the shipping contract expressly states a guarantee and its conditions. |
| Starts counting from | Use the service terms; label creation should not be assumed to start transit time before physical acceptance. |
| Main delay factors | Late tender, consolidation, weekends, holidays, peak volume, weather, remote delivery, customs, address problems, restricted goods, and partner handoffs. |
| Official source date/validity | Check the service terms attached to the shipment because route conditions and commercial commitments can change. |
|
Destination Country Delivery Times
| Destination Country / Region | Estimated Delivery Time Range |
| Destination shown on the shipment record | Use the route-specific window supplied at purchase or dispatch and recalculate from physical acceptance rather than label creation. |
View all destination delivery details
| Primary Service Type | Use the exact service stated on the order, label, manifest, or carrier record. |
| Average Delivery Days | Calculate from comparable shipments using physical acceptance and final delivery timestamps for the same route and service. |
| Last-Mile Partner / Handoff Carrier | Use the carrier identified by the latest handoff or destination acceptance event. |
| Customs & Clearance Tips | Ensure the consignee name, address, contact information, item description, value, origin, invoice, tax data, and permits match destination requirements. |
|
Pro Tip: Do not substitute generic country averages for the service purchased on a CGSD-linked shipment. Route, service level, customs requirements, tender time, and the destination delivery carrier materially affect the result.
Common Tracking Problems and Solutions
Start with the latest timestamp and identify who physically held the parcel at that point. Contact the seller for order-data or refund issues, and contact the named carrier for transport scans, delivery evidence, or facility action.
Problem & Solution
| Problem/status shown | Immediate action |
| Invalid number or no result | Copy the number again, preserve letters and zeroes, remove formatting spaces, and confirm it is not an order ID. |
View all details for an invalid number| Likely cause | Typing error, wrong identifier type, unactivated shipment record, or incorrect carrier selection. |
|---|
| Check first | Compare the value character by character with the dispatch notice. |
|---|
| When to escalate | Escalate to the seller after the promised dispatch period passes without a usable shipment identifier. |
|---|
| Who to contact | Seller or marketplace first. |
|---|
|
| Shipment information received | Ask the seller whether the parcel was physically handed over and on what date. |
View all details for pre-shipment status| Likely cause | A label or electronic record was created before carrier acceptance. |
|---|
| Check first | Seller dispatch date and any physical receipt scan. |
|---|
| When to escalate | When the seller's dispatch commitment has passed. |
|---|
| Who to contact | Seller or shipping party. |
|---|
|
| No update or stuck in transit | Check whether the parcel is between facilities, in a consolidated movement, at customs, or awaiting a partner scan. |
View all details for no tracking update| Likely cause | Long transport leg, missed scan, batch processing, customs, operational disruption, or handoff delay. |
|---|
| Check first | Latest location, responsible carrier, service window, and any linked number. |
|---|
| When to escalate | When the shipment exceeds its documented delivery window or an event requests action. |
|---|
| Who to contact | The carrier named in the latest physical scan; the seller may need to open a contractual inquiry. |
|---|
|
| Partner awaiting handoff | Wait for the partner's first physical receipt scan and keep tracking both identifiers. |
View all details for partner handoff| Likely cause | Electronic pre-advice reached the partner before the parcel. |
|---|
| Check first | The last carrier with a physical acceptance or departure event. |
|---|
| When to escalate | When the documented route window is exceeded without partner acceptance. |
|---|
| Who to contact | The seller or the last carrier that physically scanned the parcel. |
|---|
|
| Address issue or failed delivery | Follow the event instruction and contact the named last-mile carrier before return processing advances. |
View all details for an address or delivery failure| Likely cause | Incomplete address, access problem, absent recipient, signature requirement, or local delivery restriction. |
|---|
| Check first | Delivery notice, address on the order, and facility or carrier named in tracking. |
|---|
| When to escalate | Act immediately when tracking requests pickup, address confirmation, or redelivery action. |
|---|
| Who to contact | Named last-mile carrier; contact the seller if only the shipper can authorize a correction. |
|---|
|
| Customs hold | Check messages for document, tax, identity, permit, or invoice requests and respond through the named official channel. |
View all details for a customs hold| Likely cause | Routine review, missing data, valuation, tax, restricted goods, inspection, or broker processing. |
|---|
| Check first | Consignee contact details and requests from customs, the broker, carrier, or seller. |
|---|
| When to escalate | When a response deadline is stated or the broker requests shipper action. |
|---|
| Who to contact | Named broker or carrier; the seller supplies commercial documents when required. |
|---|
|
| Delivered but not received | Check the stated location, household, reception, neighbours, secure places, and parcel lockers, then request delivery evidence. |
View all details for delivered but not received| Likely cause | Alternative placement, reception handoff, locker delivery, address mismatch, premature scan, or misdelivery. |
|---|
| Check first | Delivery timestamp, exact delivery wording, proof of delivery, photo, signature, and address used. |
|---|
| When to escalate | After immediate local checks fail or the delivery evidence does not match the address. |
|---|
| Who to contact | Named delivery carrier for scan evidence and the seller for a commercial resolution. |
|---|
|
| Lost or damaged | Preserve packaging, contents, labels, photos, invoices, and tracking records; notify the seller promptly. |
View all details for loss or damage| Likely cause | Transport loss, handling damage, missing contents, packaging failure, or delivery dispute. |
|---|
| Check first | Shipping contract, declared value, insurance terms, delivery evidence, and condition at receipt. |
|---|
| When to escalate | Immediately after discovery and within the filing window stated in the applicable transport or sales terms. |
|---|
| Who to contact | The shipper usually handles a carrier claim when it owns the transport contract; the buyer contacts the seller for replacement or refund rights. |
|---|
|
International Shipping, Customs and Carrier Handoffs
For an international CGSD-linked shipment, tracking may combine seller data, origin handling, export processing, line-haul, import customs, and destination delivery events. Electronic pre-advice is not physical handover, and arrival in the destination country is not customs release.
International Flow
| Stage | Typical tracking event |
| Shipment creation | Shipment information received |
View all details for shipment creation| Physical custodian/responsible entity | Seller or shipping party until physical tender. |
|---|
| What is happening | A label, manifest, or electronic shipment record is created. |
|---|
| Can the tracking number change? | A merchant reference may later be linked to a carrier or partner number. |
|---|
| Normal visibility gap | No transport scan appears before physical acceptance. |
|---|
| What the customer should do | Confirm the dispatch commitment with the seller. |
|---|
|
| Origin acceptance and sorting | Accepted, received, or processed at facility |
View all details for origin processing| Physical custodian/responsible entity | The facility or carrier named in the acceptance event. |
|---|
| What is happening | The parcel is weighed, sorted, consolidated, or routed for export. |
|---|
| Can the tracking number change? | A consolidation or line-haul reference may be added. |
|---|
| Normal visibility gap | Events may pause while a consolidated load is built. |
|---|
| What the customer should do | Monitor the departure or export-processing event. |
|---|
|
| Export controls and line-haul | Export processing, departure, or dispatched to destination |
View all details for export and line-haul| Physical custodian/responsible entity | Export facility, security authority, broker, airline, or line-haul operator. |
|---|
| What is happening | Security review, export formalities, loading, and international transport. |
|---|
| Can the tracking number change? | The customer number may remain unchanged while internal transport references are used. |
|---|
| Normal visibility gap | There may be no public scan during flight, transit, or sealed-container movement. |
|---|
| What the customer should do | Wait for a destination-arrival event unless documents are requested. |
|---|
|
| Import customs | Arrived at destination, customs processing, held, or released |
View all details for import customs| Physical custodian/responsible entity | Carrier-controlled customs facility, broker, or customs authority. |
|---|
| What is happening | Entry data, value, taxes, admissibility, permits, and shipment contents may be reviewed. |
|---|
| Can the tracking number change? | A broker or destination-carrier reference may be linked. |
|---|
| Normal visibility gap | Customs review does not follow a universal fixed duration. |
|---|
| What the customer should do | Respond to legitimate document or payment requests and verify the requesting party. |
|---|
|
| Partner handoff | Pre-advised to partner, handed over, or partner acceptance |
View all details for partner handoff| Physical custodian/responsible entity | The last entity with a physical scan remains the best evidence of custody until the partner scans receipt. |
|---|
| What is happening | Shipment data and then the physical parcel are transferred between networks. |
|---|
| Can the tracking number change? | Yes. A destination or last-mile number may be added, while the original number may continue to work. |
|---|
| Normal visibility gap | A gap can occur between electronic pre-advice, physical transfer, and the partner's first scan. |
|---|
| What the customer should do | Track both identifiers and distinguish pre-advice from physical acceptance. |
|---|
|
| Destination delivery | At local facility, out for delivery, delivered, pickup, or exception |
View all details for destination delivery| Physical custodian/responsible entity | The destination or last-mile carrier named in the event. |
|---|
| What is happening | Local sorting, route assignment, pickup handling, delivery, or return processing. |
|---|
| Can the tracking number change? | The partner number may become the most detailed source for final-mile events. |
|---|
| Normal visibility gap | Local systems may publish events later than the physical scan. |
|---|
| What the customer should do | Follow the last-mile carrier's delivery or pickup instruction. |
|---|
|
Delivery Management and Post-shipment Options
A request to change delivery does not guarantee that the route can be altered. Use the carrier named in the latest event and expect identity, address, shipper-authorization, service, customs, security, and operational checks.
Delivery Management
| Option | Who can request |
| Address review or correction request | The shipper may need to authorize changes; the recipient can report an error to the named delivery carrier. |
View all details for an address request| Eligibility | Depends on shipment stage, service rules, customs data, fraud controls, and shipper authority. |
|---|
| Deadline/available stage | Request action before final delivery or return processing whenever tracking identifies an address problem. |
|---|
| Fee | Any charge must be checked with the party accepting the request. |
|---|
| Guaranteed? | No; a submitted request may be rejected or arrive too late. |
|---|
| Official action link | CGSD website |
|---|
|
| Redelivery, pickup, or delivery-instruction request | The recipient follows the notice or contacts the last-mile carrier named in tracking. |
View all details for redelivery or pickup| Eligibility | Depends on the destination carrier, service, parcel status, identity checks, and local facility rules. |
|---|
| Deadline/available stage | Follow the deadline stated in the delivery exception or pickup notice. |
|---|
| Fee | Use the destination carrier's current terms. |
|---|
| Guaranteed? | No; operational, security, sender, and service restrictions may apply. |
|---|
| Official action link | Use the destination carrier link or contact details displayed in the tracking result or delivery notice. |
|---|
|
| Proof of delivery request | Recipient or shipper, subject to the delivery carrier's access and privacy rules. |
View all details for proof of delivery| Eligibility | Depends on whether the purchased service captured a signature, photo, coordinates, recipient name, or delivery-location record. |
|---|
| Deadline/available stage | After a delivered event appears. |
|---|
| Fee | Use the applicable service terms. |
|---|
| Guaranteed? | The evidence available depends on the purchased service and local privacy rules. |
|---|
| Official action link | Contact the carrier named in the delivered event. |
|---|
|
Lost, Damaged, Claims, Insurance and Refunds
A tracking inquiry, carrier loss investigation, insurance claim, transport-fee refund, and seller refund are separate processes. Preserve the parcel, packaging, label, contents, photos, invoice, value evidence, and all tracking records.
Claims and Refunds
| Process | Use when |
| Tracking inquiry | A scan is unclear, missing, delayed, or inconsistent with the physical shipment. |
View all details for a tracking inquiry| Who files | Recipient may ask for information; the shipper may need to open a contractual investigation. |
|---|
| Earliest/latest filing time | Use the purchased service terms and act when the documented delivery window is exceeded or an exception requests action. |
|---|
| Required evidence | Tracking number, shipment date, latest event, service, addresses, and contents description. |
|---|
| Possible outcome | Scan explanation, facility search, delivery evidence, request for more data, or escalation to a formal claim. |
|---|
| Official link | CGSD website |
|---|
|
| Carrier loss, damage, or missing-contents claim | The transport contract provides a claim path and the shipment is lost, damaged, or incomplete. |
View all details for a carrier claim| Who files | The transport-contract holder, commonly the shipper, unless the carrier permits another party. |
|---|
| Earliest/latest filing time | Use the exact service and contract terms; notify the responsible party promptly after discovery. |
|---|
| Required evidence | Waybill, invoice, value proof, photos, damage report, packaging, contents, and insurance or declared-value record. |
|---|
| Possible outcome | Investigation, settlement under applicable liability terms, denial, or request for more evidence. |
|---|
| Official link | Use the claim channel provided in the shipper's transport contract. |
|---|
|
| Seller replacement or refund | The buyer seeks a commercial remedy for non-delivery, damage, incorrect goods, or missing contents. |
View all details for a seller remedy| Who files | The buyer opens the request with the seller or marketplace. |
|---|
| Earliest/latest filing time | Use the order platform's buyer-protection and dispute deadlines. |
|---|
| Required evidence | Order number, tracking, delivery evidence, photos, messages, and item or payment records. |
|---|
| Possible outcome | Replacement, refund, partial refund, further investigation, or rejection under sales terms. |
|---|
| Official link | Use the order page or marketplace dispute channel. |
|---|
|
17TRACK can display available tracking data but cannot approve a claim, determine legal liability, reimburse postage, or issue a merchant refund.
Shipping Restrictions and Special Handling
Before shipping, check the current CGSD acceptance terms, origin and destination law, customs requirements, airline or surface-transport rules, and any partner restrictions. Acceptance by a seller does not establish carrier or customs admissibility.
Shipping Restrictions
| Category | Prohibited or restricted |
| Dangerous goods | Ship only when the exact commodity, route, service, documentation, packaging, quantity, and transport mode are accepted. |
View all details for dangerous goods| Typical examples | Flammable, explosive, corrosive, toxic, pressurized, oxidizing, or otherwise regulated materials. |
|---|
| Key condition/packaging | Classification, marking, labels, declarations, approved packaging, and trained handling may be required. |
|---|
| Transport limitation | Air, road, rail, sea, postal, and destination rules can differ. |
|---|
| Possible tracking/delivery impact | Security hold, inspection, rerouting, refusal, return, disposal, or enforcement action. |
|---|
| Official rules | Use current carrier terms and the laws governing every route segment. |
|---|
|
| Lithium batteries and electronic devices | Restrictions depend on battery chemistry, watt-hour rating, quantity, condition, device installation, packaging, and transport mode. |
View all details for batteries| Typical examples | Phones, laptops, power banks, loose cells, damaged batteries, and battery-powered equipment. |
|---|
| Key condition/packaging | Prevent short circuits, movement, accidental activation, and physical damage; declarations and labels may apply. |
|---|
| Transport limitation | Loose, defective, recalled, or oversized batteries may face stronger restrictions. |
|---|
| Possible tracking/delivery impact | Security screening, route change, refusal, return, or disposal under applicable rules. |
|---|
| Official rules | Confirm acceptance before tender with the contracted shipping party. |
|---|
|
| Liquids, perishables, medicines, and biological materials | Acceptance depends on leakage risk, temperature, shelf life, licensing, packaging, route, and destination controls. |
View all details for sensitive contents| Typical examples | Cosmetics, food, supplements, prescription items, laboratory samples, and temperature-sensitive products. |
|---|
| Key condition/packaging | Leakproof containment, absorbent material, temperature controls, permits, and accurate declarations may be required. |
|---|
| Transport limitation | Transit time and customs review may make some routes unsuitable. |
|---|
| Possible tracking/delivery impact | Inspection, document request, delay, spoilage risk, refusal, or destruction. |
|---|
| Official rules | Check carrier, customs, health, agriculture, and destination rules before shipping. |
|---|
|
| High-value, controlled, counterfeit, or unlawful goods | Goods must be lawful, accurately declared, and eligible under the route and service terms. |
View all details for controlled or high-value goods| Typical examples | Currency, jewellery, weapons, controlled substances, protected wildlife products, counterfeit goods, and restricted technology. |
|---|
| Key condition/packaging | Licences, permits, valuation documents, secure packaging, and special services may be required. |
|---|
| Transport limitation | Some goods or routes may be prohibited regardless of packaging. |
|---|
| Possible tracking/delivery impact | Customs hold, seizure, investigation, refusal, or return. |
|---|
| Official rules | Obtain route-specific legal and carrier guidance before tender. |
|---|
|
Customer Service
Use the supplied CGSD website for carrier-side information and the seller for order, payment, replacement, or refund issues. For final-mile problems, contact the destination carrier identified in the latest tracking event.
Customer Service
| Channel | Verified contact/link |
| CGSD website | http://www.szcgsd.com/ |
View all details for the CGSD website
| Best for | Carrier information and any tracking or contact options presented by CGSD. |
| Region/language | Use the options displayed on the website. |
| Hours and time zone | Use any current service schedule displayed by the website contact channel. |
| Information to prepare | Tracking number, shipping date, origin, destination, service, latest event, contents description, and contact details. |
| Important limitation | The transport-contract holder may need to authorize an investigation, claim, address change, or other shipment action. |
|
| Seller or marketplace | Use the order page, seller message channel, or marketplace dispute process. |
View all details for seller support
| Best for | Wrong or missing tracking number, non-dispatch, product issues, replacement, and buyer refund requests. |
| Region/language | According to the marketplace or seller account. |
| Hours and time zone | Use the service schedule shown in the order-support channel. |
| Information to prepare | Order number, tracking number, promised dispatch and delivery dates, payment record, messages, photos, and requested remedy. |
| Important limitation | A seller controls commercial remedies but does not control customs decisions or scans made by a carrier. |
|
| Destination or last-mile carrier | Use the carrier and linked identifier shown in the latest handoff or destination event. |
View all details for last-mile support
| Best for | Delivery attempt, pickup, local address issue, proof of delivery, misdelivery, or local-facility questions. |
| Region/language | Depends on the destination carrier. |
| Hours and time zone | Use the current hours stated by the destination carrier. |
| Information to prepare | Original and partner tracking numbers, delivery address, delivery notice, latest event, and recipient identification where required. |
| Important limitation | The destination carrier may refer contractual claims or major address changes back to the shipper. |
|
Ecommerce and Business Tracking
Merchants should preserve the original CGSD-linked identifier, any partner identifier, carrier attribution, raw event text, normalized status, event time, location, and exception reason. This supports customer notifications, handoff analysis, delivery disputes, and carrier-performance review.
Developer/API Comparison
| Option | Provider |
| Consumer website tracking | CGSD |
View all details for CGSD website tracking
| Carrier coverage | CGSD-linked shipments and any partner events exposed through the website. |
| Primary use | Manual shipment lookup. |
| Authentication | Use the access process presented by the website. |
| Tracking/batch/webhook capability | Use only capabilities expressly presented in the current interface or contractual documentation. |
| Current developer documentation | CGSD website |
| Migration/deprecation note | Validate integrations against current documentation before production use. |
|
| Multi-carrier Tracking API | 17TRACK |
View all details for the 17TRACK API
| Carrier coverage | Multi-carrier tracking through the 17TRACK platform. |
| Primary use | Registering and monitoring shipments across carrier networks. |
| Authentication | The registration request uses the 17token header. |
| Tracking/batch/webhook capability | Use the capabilities and limits documented for the selected 17TRACK API product. |
| Current developer documentation | 17TRACK API documentation |
| Migration/deprecation note | Pin integrations to the documented API version and review release or migration guidance before changing endpoints. |
|
FAQ
1. How do I track my CGSD package?Enter the shipment tracking number on the supplied CGSD website or track it with 17TRACK to view available events. Use the exact identifier from the shipping record and preserve any partner number shown later.
2. Where can I find my CGSD tracking number?Look on the order page, dispatch email, shipping label, receipt, or seller message. If you only have an order number, ask the seller for the associated tracking or waybill number.
3. What does a CGSD tracking number look like?Use the complete alphanumeric value labelled as the tracking, logistics, shipment, or waybill number in your shipping record. Do not identify the service from a prefix alone, and do not remove letters or leading zeroes.
4. When will the first CGSD tracking event appear?The first transport event normally depends on physical acceptance or facility processing. A label-created event only proves that electronic shipment data exists, so ask the seller for the physical handover date if no acceptance scan appears.
5. Why is my CGSD tracking not updating?The parcel may be between facilities, inside a consolidated movement, undergoing customs processing, or awaiting a partner scan. Check the latest responsible carrier and escalate when the documented service window is exceeded.
6. How long does CGSD delivery take?Use the service-specific delivery window supplied in the order or shipping contract. Count from the event required by those terms rather than assuming that label creation started physical transit.
7. What should I do after a failed CGSD delivery attempt?Follow the tracking event or delivery-notice instruction and contact the named last-mile carrier promptly. Redelivery, pickup, or address action depends on local rules and the shipment's current stage.
8. What should I do if CGSD tracking says delivered but I have no package?Check the stated delivery place, household members, reception, neighbours, secure locations, and parcel lockers first. Then request proof of delivery from the named delivery carrier and notify the seller if the parcel remains missing.
9. How do I report a lost or damaged CGSD shipment?Preserve the packaging, label, contents, photos, invoice, value proof, and tracking record, then notify the seller promptly. The shipper may need to file the transport claim because it commonly owns the carrier contract.
10. How do I contact CGSD?Use the contact options presented on the supplied CGSD website and prepare the tracking number, shipping date, route, latest event, addresses, and contents description. Contact the seller for order or refund matters.
11. Why can a CGSD-linked shipment show another carrier?A shipment can move through different origin, line-haul, customs, and last-mile networks. The event history should identify which carrier controls the current stage, while CGSD remains the carrier identity associated with the original tracking request.
12. Does electronic pre-advice mean the partner has my CGSD package?No, electronic pre-advice alone does not prove physical custody. Look for the partner's first received, accepted, or processed scan before treating the handoff as complete.
13. Can a CGSD shipment receive a second tracking number?Yes, a partner or last-mile carrier may assign a linked identifier during handoff or relabelling. Keep both values because each support team may require the number used in its own network.
14. Does arrival in the destination country mean a CGSD shipment cleared customs?No, destination arrival and customs release are separate events. Import processing may still require inspection, tax payment, identity information, permits, invoices, or corrected declarations.
15. Who should open a CGSD transport investigation?The transport-contract holder, commonly the shipper, may need to open the formal investigation. A recipient can report a problem and request delivery evidence, while the seller handles the buyer's commercial remedy.
16. Is a CGSD estimated delivery date guaranteed?An estimated date is not a guarantee unless the purchased service terms expressly state a guarantee and its conditions. Customs, handoffs, weather, peak volume, remote delivery, and address issues can change an estimate.
17. Can businesses track CGSD shipments through an API?Businesses can use a documented carrier integration supplied under their CGSD arrangement or a multi-carrier platform such as the 17TRACK API. Production systems should preserve raw events, normalized statuses, partner identifiers, timestamps, and carrier attribution.
Tracking API
Use only current CGSD integration documentation supplied through the applicable business arrangement. The 17TRACK registration example below retains the carrier-code placeholder because the code should be selected from current 17TRACK carrier data rather than inferred from the brand name.
# 1. CGSD official tracking API
# Use only the current endpoint, method, authentication, headers,
# request body, and service codes supplied in CGSD developer or
# contractual integration documentation.
# No speculative CGSD request is included.
# 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"
}
]'
# Replace TRACKING_NUMBER with the shipment identifier.
# Replace CARRIER_CODE with the current code from 17TRACK carrier data.
# Documentation: https://api.17track.net/en/doc
Sources & References
17TRACK is an independent tracking platform and is not affiliated with CGSD.