Melhor Envio Tracking

Important: Melhor Envio is not a carrier

Melhor Envio describes itself as a freight-management and logistics-intermediation platform.

It does not physically transport parcels.

The operational model is:

Melhor Envio
→ quote, service comparison, label, posting access, tracking aggregation and support mediation

selected carrier
→ physical collection, transport, delivery attempts, delivery, proof, incident analysis and return

This distinction controls the entire page.

Do not interpret a Melhor Envio brand, label or dashboard status as proof that Melhor Envio physically handled the parcel.

Corporate and contracting context

Melhor Envio is part of the LWSA ecosystem. LWSA’s corporate history states that it acquired Melhor Envio in 2020.

Official Melhor Envio materials reviewed for this page use more than one legal presentation in different documents. The contracting entity can depend on the current terms, invoice, branch or business relationship.

Public-safe rule:

Use the current account terms, invoice or contract to identify the legal contracting entity. Do not infer it from the Melhor Envio brand alone.

This legal detail does not change the operational boundary:

platform or contracting entity
→ freight intermediation, label, account and support

selected carrier
→ physical transport

Domestic shipping scope

Current official platform guidance describes the available carrier services as domestic transport within Brazil.

A shipment involving imported goods can still use Melhor Envio for a later domestic leg, but that does not make Melhor Envio an international forwarding carrier or customs authority.

Track a shipment generated through Melhor Envio

Use the carrier tracking code shown in:

• the Melhor Envio dashboard;
• Meus Envios;
• the tracking page shared by the sender;
• the carrier label;
• the selected carrier’s official tracking page.

Enter one supported code at a time.

Do not enter:

• CPF;
• CNPJ;
• recipient name;
• phone number;
• email address;
• complete address;
• invoice number;
• fiscal document;
• label authorization code;
• payment reference;
• support ticket;
• claim reference;
• proof-of-delivery document.

An ORD protocol should be treated as private platform data unless the current carrier-specific workflow explicitly confirms that it can resolve the shipment.

Find the actual carrier first

A Melhor Envio shipment can use different physical carriers.

The selected carrier depends on:

• origin and destination;
• service purchased;
• parcel dimensions and weight;
• posting method;
• carrier availability;
• merchant choice.

The public tracking page should display:

• platform context: Melhor Envio;
• responsible physical carrier;
• carrier tracking code;
• latest event;
• raw carrier wording where useful;
• last update time.

Melhor Envio shipment
≠ one universal carrier

If the carrier cannot be identified safely, do not force a generic Melhor Envio carrier lock.

Which carriers work with Melhor Rastreio?

A dedicated official Help Centre article updated in July 2026 lists the following integrated carriers:

• Azul Cargo Express;
• Buslog;
• Correios;
• Jadlog;
• J&T Express;
• LATAM Cargo;
• Loggi;
• Total Express.

This list is volatile.

It does not mean:

• every Melhor Envio carrier is supported;
• every shipment from these carriers is supported;
• a shipment generated outside Melhor Envio can be added;
• the list will remain unchanged.

Use the current official carrier-coverage article before relying on the list.

Melhor Rastreio is not a universal tracker

Current official guidance limits Melhor Rastreio to:

• currently integrated carriers;
• shipments generated through Melhor Envio.

An external shipment code can fail even when:

• the carrier is integrated;
• the carrier’s own website has events;
• the code is valid.

A message saying the parcel has no movement can therefore mean:

• no carrier event exists yet;
• the shipment was not generated through Melhor Envio;
• the carrier is not currently integrated;
• the reference requires a carrier-specific input form;
• synchronization has not completed.

Do not treat that message as proof that the physical parcel is stationary.

Older guidance about external tracking codes

An older official article indicated that some externally generated shipments could be added.

Current Help Centre guidance says external shipments cannot be added, even for currently integrated carriers.

Use the current Help Centre rule.

valid external carrier code
≠ supported Melhor Rastreio shipment

Carrier tracking code versus `ORD`

The two identifiers have different jobs.

Current general guidance says the ORD protocol:

• is an internal shipment code;
• should not be sent to the recipient;
• has no general tracking utility.

Public default:

ORD
≠ carrier tracking code

The Total Express `ORD` exception

A current Total Express-specific article says Melhor Rastreio can accept:

• the Total Express carrier code;
• the Melhor Envio ORD code;

for that carrier workflow.

This does not establish universal ORD support.

Possible explanations include:

• a carrier-specific alias;
• an internal mapping;
• a newer integration not reflected in general help;
• different behaviour between Melhor Rastreio and the carrier’s own website.

Use this rule:

Accept ORD only after the underlying carrier and current workflow are verified. Preserve the carrier tracking code as the primary identifier.

Can I track with a store order number?

Not by default.

A retailer order number identifies the commercial purchase.

The same order can contain:

• several labels;
• several parcels;
• several carriers;
• several tracking codes.

merchant order
≠ Melhor Envio shipment protocol
≠ carrier tracking code

Only an officially linked platform reference can resolve a shipment.

Ask the merchant for:

• carrier name;
• carrier tracking code;
• separate codes for every parcel.

One order can contain several parcels

One ecommerce order can be split because of:

• stock location;
• package size;
• weight;
• product handling;
• carrier service;
• fulfilment timing.

Each parcel can have an independent:

• label;
• tracking code;
• carrier;
• status;
• delivery date;
• return path.

one parcel Delivered
≠ entire order Delivered

Platform order object versus physical parcel

Melhor Envio creates an internal order or shipment object before physical transport.

The platform can store:

• internal ID;
• ORD protocol;
• label ID;
• authorization code;
• carrier tracking code;
• label status;
• tracking URL;
• carrier and service data.

These fields do not carry the same evidence.

Do not collapse them into one “tracking number.”

Label lifecycle versus carrier movement

The platform lifecycle can include:

• order created;
• pending;
• released;
• generated;
• received;
• posted;
• delivered;
• cancelled;
• undelivered;
• paused;
• suspended.

These are Melhor Envio or integration lifecycle states.

They are not one complete carrier event dictionary.

The carrier timeline separately records:

• acceptance;
• collection;
• sorting;
• transfer;
• route;
• attempt;
• delivery;
• exception;
• return.

`order.created`

Strongest supported conclusion:

A Melhor Envio shipment object exists.

It does not prove:

• payment;
• label generation;
• posting;
• Ponto Parceiro receipt;
• carrier collection.

`order.pending`

A pending state can mean the platform operation has not completed.

The precise reason can depend on:

• payment;
• label release;
• processing;
• account or carrier response.

pending
≠ carrier possession

`order.released`

Current developer documentation associates order.released with the label payment or release stage.

order.released
→ label was paid or released
≠ label printed
≠ parcel posted
≠ carrier collected

`order.generated`

This state confirms the transport label was generated.

order.generated
→ label exists
≠ parcel physically left the sender

A seller can generate a label and never post the parcel.

Printed label does not mean shipped

Printing is a sender action.

It does not prove:

• drop-off;
• collection;
• posting-point receipt;
• carrier acceptance;
• transport movement.

Use Label Created for the general evidence boundary.

`order.received`

Current webhook documentation describes order.received in relation to receipt at a Pegaki distribution point.

Strongest supported conclusion:

The parcel entered the posting-point or Pegaki distribution workflow.

It does not universally prove:

• selected carrier collection;
• carrier depot acceptance;
• line-haul departure.

Preserve the actual posting-point event.

`order.posted`

A posted lifecycle event indicates the platform recorded a posting stage.

The physical meaning still depends on:

• direct carrier unit;
• Ponto Parceiro;
• Pegaki route;
• carrier integration;
• event source.

A later explicit carrier-collected event is stronger selected-carrier custody evidence.

`order.delivered`

This state records a platform delivery completion.

Preserve:

• responsible carrier;
• raw carrier event;
• delivery subtype;
• source timestamp.

platform Delivered
≠ named buyer independently authenticated
≠ contents or condition proved

Cancelled, paused and suspended are different

Cancelled

A platform or label operation was cancelled.

Paused

A platform lifecycle or processing branch is paused.

Suspended

A suspension workflow or state exists.

None should be treated automatically as:

• physical interception;
• return movement;
• sender receipt.

A later carrier event is stronger physical evidence.

Label validity and posting windows

Current label instructions distinguish:

• payment;
• generation;
• printing;
• posting.

A label can expire or become unusable before posting.

The applicable window depends on:

• current platform rules;
• carrier;
• service;
• label state.

Do not turn a label-validity window into a delivery estimate.

Expired label

An expired label means the sender can no longer use it under the current rule.

It does not mean:

• parcel delivered;
• carrier returned parcel;
• carrier lost parcel.

If no physical acceptance occurred, the problem remains with the sender’s platform workflow.

Cancelled label versus delivery suspension

Cancelling a label before posting is a platform action.

Requesting suspension after carrier custody is a carrier-treatment request.

label cancelled before posting
≠ parcel intercepted after posting

Why can a label remain `Released` after posting?

Current official support recognizes cases where a label still appears as released after physical posting.

The sender may need:

• posting receipt;
• support treatment;
• lifecycle correction.

This confirms that a platform label state can lag behind physical reality.

label still Released
≠ parcel definitely not posted

Use physical receipts and carrier events as stronger evidence.

Tracking code can appear after posting

Current webhook documentation says the carrier tracking parameter can take up to one business day after posting to appear, depending on the carrier.

parcel posted
+ carrier code absent
≠ posting necessarily failed

The sender should keep:

• posting receipt;
• platform order;
• carrier and service;
• date and location.

Carrier-specific input transformations

Different carrier websites can require different input handling.

Official Melhor Envio guidance documents examples such as:

• entering only the numeric part of a displayed code;
• removing a platform prefix;
• splitting an AWB or CTe reference;
• using a carrier-specific field;
• providing recipient CPF or CNPJ in the carrier’s authenticated form.

11Tracking must not request CPF or CNPJ.

When personal identity is required, use the carrier’s official site.

Ponto Parceiro is not the carrier

A Ponto Parceiro can receive the parcel from the sender and forward it through a posting network.

It can act as:

• drop-off point;
• consolidation point;
• transfer node.

It is not necessarily the selected carrier.

parcel left at Ponto Parceiro
≠ carrier collected it

Ponto Parceiro custody ladder

Received at Ponto Parceiro

This event proves more than label creation.

It supports:

The parcel was physically handed to the posting-point network.

It does not prove:

• selected carrier has collected it;
• carrier liability has begun under every contract;
• line-haul started.

Entered Ponto Parceiro distribution centre

This status indicates movement within the posting-point network.

point distribution centre
→ pre-carrier or consolidation movement recorded
≠ selected carrier depot

Wait for a carrier collection event.

Collected by carrier

This is stronger evidence that the selected physical carrier has the parcel.

It does not yet prove:

• departure from origin facility;
• destination arrival;
• delivery route.

Use Carrier Received Package for the general custody boundary.

Carrier posting point versus Ponto Parceiro

A parcel can be posted:

• directly at a carrier unit;
• at a Melhor Envio partner point;
• through a Pegaki or related point flow;
• through a collection service.

The same normalized word “posted” can conceal different custody paths.

Preserve:

• actor;
• location;
• timestamp;
• raw event wording.

Melhor Rastreio versus the carrier tracker

Melhor Rastreio aggregates events from the selected carrier.

The carrier’s official tracker can be the stronger source when:

• a new carrier event has not synchronized yet;
• the raw carrier wording contains more detail;
• the carrier requires a transformed code;
• proof or recipient confirmation requires an authenticated flow;
• a carrier-specific exception is not represented in normalization.

Melhor Rastreio can be useful for:

• identifying the responsible carrier;
• sharing one tracking page;
• viewing normalized movement;
• seeing the last synchronization;
• receiving configured email notifications.

Use both sources without treating either as continuous GPS.

How often Melhor Rastreio updates

Current official guidance says:

1. the platform queries the carrier immediately when a code is added;
2. it then checks for updates every two hours;
3. monitoring continues for 30 days.

carrier event exists
→ Melhor Rastreio may show it after synchronization

This is periodic synchronization, not a live carrier stream.

Why the two trackers can disagree

Possible causes include:

• the carrier has a newer event;
• two-hour synchronization interval;
• carrier API latency;
• event normalization;
• carrier-specific input transformation;
• platform shipment not generated through Melhor Envio;
• unsupported carrier;
• delayed carrier tracking-code assignment;
• different event timestamps or time zones;
• carrier correction or backfill.

Compare:

• carrier name;
• tracking code;
• raw event;
• location;
• event time;
• last update time.

Do not assume fraud or data loss from one temporary mismatch.

Last update time is not the event time

A tracking page can contain:

• event time supplied by the carrier;
• time Melhor Rastreio retrieved the event;
• page refresh time.

These are not interchangeable.

last platform update
≠ exact time parcel moved

The raw carrier event time is usually the stronger logistics timestamp when available.

Tracking notifications

Melhor Rastreio can send email notifications.

The sender can:

• enable or stop notifications;
• add email addresses;
• share the tracking link.

A recipient email supplied during label generation can be selected for notifications.

Notification subscription does not prove:

• parcel ownership;
• recipient identity;
• delivery;
• authority to change the shipment.

Keep email addresses private.

Tracking-link privacy

A shared tracking page can expose:

• carrier;
• tracking code;
• events;
• dates;
• locations.

Do not put a complete tracking link in:

• metadata;
• social previews;
• public examples;
• screenshots with personal data;
• analytics labels;
• public support posts.

What does the location in Melhor Rastreio mean?

The location can identify:

• carrier unit responsible for the event;
• transfer terminal;
• distribution centre;
• origin or destination branch;
• posting-point network node.

It is not always the recipient’s city.

event city differs from destination
≠ parcel is necessarily going the wrong way

A nearby regional unit can serve several municipalities.

Location and route evidence

Use the location together with:

• event type;
• responsible carrier;
• previous and next scans;
• direction of movement;
• route stage.

A single city name does not prove:

• exact parcel location;
• final destination;
• wrong route;
• live GPS.

Normalized status versus raw carrier wording

Melhor Rastreio can normalize carrier events into common categories.

Normalization is useful, but it can hide:

• specific address problem;
• pickup instruction;
• incident suspicion;
• carrier unit;
• return reason;
• proof subtype.

The public timeline should preserve safe raw wording when it changes the user’s next action.

Posted, received or deposited by carrier

These terms can indicate carrier acceptance.

However, the physical meaning depends on:

• direct carrier posting;
• partner-point posting;
• collection;
• carrier integration;
• event source.

Strongest supported conclusion:

A carrier or posting workflow recorded receipt.

A later explicit carrier collection or departure event can be stronger.

`CTe emitido`

CTe refers to a Brazilian electronic freight document.

A CTe emitido event confirms:

• the freight document was issued.

It does not prove:

• carrier physically collected the parcel;
• truck departed;
• line-haul movement started.

CTe issued
→ transport document exists
≠ physical movement

Wait for a physical carrier event.

Transfer departure

A departure event supports:

The parcel left one carrier unit or transfer point.

It does not prove:

• arrival at the next facility;
• destination city;
• Out for Delivery.

Transfer arrival

An arrival event supports:

The parcel entered another carrier unit or transfer point.

It does not prove:

• delivery route;
• recipient availability;
• same-day delivery.

Out for Delivery

Out for Delivery means the selected carrier recorded route activity.

Out for Delivery
→ carrier route activity exists
≠ live vehicle location
≠ exact arrival time
≠ guaranteed delivery that day

A later event can include:

• Delivered;
• recipient absent;
• address issue;
• route delay;
• pickup instruction;
• return.

Delivered

A Delivered event confirms a carrier or platform completion record.

Preserve the subtype where available:

• recipient;
• third party;
• reception;
• pickup;
• proof;
• location;
• timestamp.

Delivered
→ completion event recorded
≠ named buyer independently authenticated
≠ contents or condition proved

Sorting or internal-processing error

An internal-processing or sorting error can represent:

• routing correction;
• missort;
• data correction;
• carrier operational exception.

It does not automatically prove:

• loss;
• permanent delay;
• wrong final destination.

Use the next event and current carrier action.

Vehicle breakdown or operational delay

A vehicle or operational problem can interrupt the planned route.

Strongest supported conclusion:

The carrier recorded an operational delay.

It does not prove:

• parcel damage;
• claim approval;
• return;
• delivery cancellation.

Weather and force-majeure event

Weather, road restrictions or force majeure can affect:

• collection;
• transfer;
• route;
• delivery estimate.

The event explains a risk to the plan.

It does not establish one universal revised delivery date.

Address not found

An address-not-found event can mean:

• carrier could not locate the address;
• route data was insufficient;
• access or mapping failed.

The sender should use Melhor Envio support because the carrier contract was generated through the platform.

Do not publish the address.

Incorrect or incomplete address

A carrier can require:

• complement;
• number;
• landmark;
• contact confirmation;
• sender instruction.

What can be corrected and how quickly depends on the carrier.

address action required
→ information or instruction needed
≠ carrier accepts every address change

11Tracking cannot change the address.

Recipient absent

Recipient absence can lead to:

• another attempt;
• instruction request;
• pickup;
• return.

The number of attempts and next action are carrier-specific.

Do not publish one universal Melhor Envio attempt count.

Recipient unknown or moved

This event can indicate the carrier could not identify the recipient at the destination.

Possible next steps:

• sender clarification;
• return;
• carrier treatment.

It does not prove the merchant used the correct address.

Location closed

A closed commercial location can produce:

• another attempt;
• instruction request;
• return;
• delay.

The carrier and service control the next branch.

Delivery refused

Refusal means the carrier recorded that delivery was not accepted.

It can lead to return.

refused
→ non-acceptance recorded
≠ seller refunded buyer

Rural or restricted-access delivery

Some carriers use special handling for:

• rural areas;
• restricted roads;
• gated locations;
• risk areas;
• limited coverage.

Possible outcomes include:

• pickup at a carrier location;
• route delay;
• service restriction;
• return.

Use the selected carrier’s current instruction.

Waiting time exceeded

A carrier can record that the allowed delivery waiting time was exceeded.

This can occur at:

• commercial address;
• reception;
• unloading point;
• restricted site.

It is an operational occurrence, not proof of recipient refusal.

Awaiting pickup by recipient

This status means the parcel is held at a named carrier location or partner point.

awaiting pickup
→ item available under a collection workflow
≠ recipient collected it

Check:

• location;
• opening hours;
• deadline;
• required identification;
• carrier instructions.

Do not infer one universal holding period.

Searches (`buscas`)

A buscas status means the carrier is searching for the shipment.

searches in progress
→ investigation exists
≠ parcel officially lost
≠ compensation approved

The sender should continue the treatment through Melhor Envio support.

Suspected loss, theft, robbery, damage or violation

Carrier wording can indicate:

• suspected loss;
• robbery or theft;
• package damage;
• violation;
• “contact your supplier”;
• another serious occurrence.

Strongest supported conclusion:

An incident or suspicion requires carrier analysis.

It does not prove:

• final liability;
• insured-value eligibility;
• reimbursement amount;
• payment start date.

Tracking not updating

Classify the last strong event.

Only label or platform lifecycle

The sender controls the next action.

Received at Ponto Parceiro

The parcel is in the posting-point network; selected-carrier collection may still be pending.

Collected by carrier

The carrier controls the next movement, with support mediated through Melhor Envio.

Carrier transfer

Compare the carrier tracker and Melhor Rastreio synchronization time.

Out for Delivery

Wait for completion or an exception event.

Search or incident

Use Melhor Envio support and carrier analysis.

Return

Track the reverse movement until sender receipt is recorded.

There is no universal number of days after which a Melhor Envio shipment is automatically lost.

Estimated delivery date

The displayed estimate depends on:

• selected carrier;
• selected service;
• origin and destination;
• posting date;
• business-day calendar;
• carrier conditions.

Current official guidance says the posting day is not counted in the estimated delivery period.

estimated delivery
→ planning estimate exists
≠ live route forecast
≠ universal guarantee

Delayed shipment

A delay should be interpreted from the last evidence stage.

No general Melhor Envio delay indemnity

Current public support guidance does not provide a general delay-indemnity workflow.

This does not settle every right under:

• carrier contract;
• merchant relationship;
• marketplace policy;
• applicable law.

late delivery
≠ automatic Melhor Envio payment
≠ automatic carrier compensation
≠ automatic buyer refund

Delivery suspension request

A sender can ask Melhor Envio to relay a request to suspend delivery and return the shipment.

suspension requested
→ request submitted for carrier treatment
≠ parcel intercepted
≠ carrier accepted request
≠ return started

Later carrier events confirm whether the request was executed.

Return to sender

A return can follow:

• refusal;
• failed delivery;
• address problem;
• pickup expiry;
• accepted suspension;
• carrier occurrence;
• service restriction.

return movement
→ reverse transport recorded
≠ sender received parcel
≠ buyer refunded

Some carrier flows continue using the same tracking code during return, but this is not universal.

Return completed

A return-completed event supports:

The carrier recorded delivery back to the sender or return destination.

It does not prove:

• buyer refund;
• replacement;
• marketplace case closure;
• claim payment.

The merchant controls the commercial outcome.

Reverse logistics

A reverse-logistics label creates a separate operational shipment.

return label created
≠ recipient posted return

return posted
≠ carrier delivered return

return delivered
≠ merchant approved refund

Track the reverse shipment with its own carrier code.

Melhor Envio support mediation

For eligible shipments generated through Melhor Envio, current official guidance routes carrier treatment through Melhor Envio support.

Melhor Envio can:

• open or relay a carrier ticket;
• request documents;
• communicate carrier feedback;
• mediate an eligible claim;
• correct some platform lifecycle records;
• relay a suspension or return request.

It cannot guarantee:

• carrier acceptance;
• immediate response;
• parcel recovery;
• delivery suspension;
• claim approval;
• reimbursement;
• merchant refund.

Why contact Melhor Envio instead of the carrier directly?

The selected carrier may have performed the physical transport, but the shipping contract or negotiated account can belong to Melhor Envio.

This can mean:

• the carrier directs the sender back to Melhor Envio;
• only Melhor Envio can open the account-level treatment;
• documents must pass through the platform;
• carrier response is returned through Melhor Envio support.

The public page should identify both actors:

physical event owner
→ selected carrier

contract and support route
→ Melhor Envio for eligible platform-generated shipment

Who should contact support?

The sender or merchant usually controls:

• Melhor Envio account;
• label purchase;
• posting receipt;
• declared or insured value;
• carrier service;
• support ticket;
• claim documents.

The recipient can provide:

• non-receipt details;
• damage photographs;
• packaging;
• delivery dispute;
• pickup problem.

For an ecommerce purchase, the recipient should also protect merchant or marketplace deadlines.

Proof of delivery

Proof depends on the selected carrier and service.

Possible proof objects include:

• electronic delivery confirmation;
• recipient name;
• signature;
• carrier image;
• pickup record;
• Correios electronic proof;
• AR or another purchased proof service;
• internal carrier record.

A proof shown through Melhor Envio can be a courtesy integration rather than a universal contractual right.

11Tracking cannot retrieve private proof.

Proof indicator versus proof document

A timeline can show that proof exists without displaying the proof itself.

proof available
→ carrier or platform indicates a proof object exists
≠ proof is public
≠ 11Tracking can retrieve it

Use the official account or carrier route.

Delivered but not received

First identify:

• selected carrier;
• raw delivery wording;
• recipient or third-party subtype;
• delivery location;
• timestamp;
• proof availability;
• pickup or reception branch.

Then:

1. check household members, reception, neighbour and safe location where relevant;
2. preserve the platform and carrier history privately;
3. ask the sender to open Melhor Envio support treatment;
4. preserve retailer or marketplace deadlines.

Delivered
≠ named buyer necessarily received
≠ proof resolves every disputed fact

Claim actor architecture

Insured or declared value

A declared or insured value can affect eligible compensation.

It does not guarantee:

• all risks are covered;
• full retail value is payable;
• delay is covered;
• prohibited contents are covered;
• proof is unnecessary;
• payment is immediate.

The selected carrier and service terms control.

Keep the value and invoice private.

Loss or robbery treatment

Current official guidance describes a mediated process after the carrier confirms a qualifying loss or robbery occurrence.

incident appears in tracking
≠ carrier confirmed loss

carrier confirms qualifying occurrence
→ claim can progress
≠ reimbursement is immediate

The timing and eligible amount vary by carrier.

Damage or package violation

Preserve:

• outer packaging;
• inner packaging;
• damaged item;
• photographs;
• invoice or proof of value;
• posting receipt;
• tracking history.

Open treatment within the applicable carrier deadline.

No universal Melhor Envio damage-reporting period is safe.

Searches are not a claim decision

A search status means the carrier is attempting to locate the parcel.

The sequence can be:

searches
→ carrier investigation
→ carrier conclusion
→ eligible claim analysis
→ possible reimbursement

Do not skip directly from “searches” to “compensation approved.”

Carrier reimbursement versus buyer refund

These are separate.

carrier indemnification
≠ recipient refund

wallet credit to sender
≠ buyer automatically paid

return to sender
≠ replacement approved

The merchant or marketplace controls the buyer-facing remedy.

Wallet credit

An eligible reimbursement can be credited to the sender’s Melhor Envio wallet under the applicable workflow.

Wallet credit is:

• an account-level platform outcome;
• not a public tracking event;
• not proof that the recipient was refunded;
• sensitive financial information.

Do not expose it in public tracking.

Metric reconciliation is not tracking

After posting, a carrier can measure actual:

• weight;
• dimensions;
• chargeable weight.

A difference can generate:

• additional charge;
• credit;
• account adjustment.

This is a billing or label-reconciliation event.

It does not mean the parcel moved, stopped or was delivered.

Posting receipt

A posting receipt can be critical evidence that the parcel entered the physical handoff process.

It can help resolve:

• label still shown as released;
• missing carrier code;
• posting-point dispute;
• claim eligibility.

Keep it private.

Privacy architecture

Melhor Envio and related service providers can process:

• CPF or CNPJ;
• sender and recipient names;
• phone and email;
• full addresses;
• order and label records;
• carrier and service data;
• invoices and declarations;
• payment and wallet data;
• tracking history;
• support tickets;
• proof and claim documents;
• device and account data.

A public tracking page should request only the minimum supported identifier.

Do not collect CPF or CNPJ

Some carrier trackers require recipient CPF or CNPJ.

11Tracking should not collect it.

Use the official carrier’s authenticated form when identity data is required.

carrier requires CPF/CNPJ
→ use official carrier flow
≠ enter personal identity into a public aggregator

Sensitive fields to suppress

Keep these out of HTML, JSON-LD, URLs, logs, analytics, cache keys, screenshots and public AI prompts:

• CPF;
• CNPJ;
• names;
• phone numbers;
• email addresses;
• complete addresses;
• invoice or NF-e data;
• contents declarations;
• insured value;
• authorization codes;
• unnecessary ORD protocols;
• payment and wallet information;
• POD;
• signatures;
• support tickets;
• claim evidence.

Verify suspicious messages

Common fraud lures can imitate:

• delivery fee;
• customs fee;
• address correction;
• release payment;
• redelivery;
• carrier occurrence;
• reimbursement;
• account verification.

Use these boundaries:

real tracking code
≠ authentic message

real carrier name
≠ safe payment link

real delivery issue
≠ payment is required

Open:

• melhorenvio.com.br independently;
• the selected carrier’s official website;
• the official Melhor Envio support area.

Do not pay through an unsolicited unknown link.

Who should act?

Use Who to Contact About a Package when the responsible actor remains unclear.

API and integration note

Melhor Envio’s developer systems expose platform and label lifecycle data.

They do not justify treating Melhor Envio as one physical carrier.

Label-status endpoint

The documented tracking endpoint is tied to a label ID and platform status.

It is not described as one complete raw carrier timeline for every transportadora.

Webhooks

Webhook events can report platform lifecycle changes such as:

• created;
• released;
• generated;
• received;
• posted;
• delivered;
• cancelled;
• undelivered;
• paused;
• suspended.

The event names must be interpreted using the current documentation and source object.

Webhook authenticity

Authenticated integrations should verify the current webhook signature method before trusting an event.

A public carrier page should not expose:

• webhook secret;
• raw payload;
• account identifiers;
• authorization data.

Retry behaviour

Webhook retries are finite.

A missing webhook does not prove the physical carrier event never occurred.

Integrations should reconcile with official API and carrier evidence.

Carrier IDs and names

Current developer documentation warns that carrier and service identifiers can differ between API versions and names can change.

Do not key production logic only by:

• display name;
• an old service ID;
• an old provider label.

Sandbox limitation

Sandbox responses are simulated integration evidence.

They do not prove production carrier behaviour, event coverage or identifier acceptance.

Frequently asked questions

Is Melhor Envio a carrier?

No. It is a shipping and freight-intermediation platform. The selected carrier physically transports the parcel.

Who actually delivers a Melhor Envio shipment?

The transportadora selected when the freight label was purchased.

What number should I use to track?

Use the carrier tracking code. Treat an ORD as an internal platform protocol unless the current carrier-specific workflow explicitly supports it.

Can every ORD number be tracked?

No. Current general guidance says ORD is internal. A Total Express-specific flow documents a limited exception.

Can I track with my store order number?

Not by default. Ask the merchant for the carrier name and carrier tracking code.

Can one order have several tracking codes?

Yes. Each physical parcel can have its own carrier, code and status.

Does a paid label mean the carrier has the parcel?

No. Payment or release is a platform label stage.

Does a generated label mean the parcel shipped?

No. Posting and carrier collection remain separate.

What does order.received mean?

Current webhook documentation associates it with receipt at a Pegaki distribution point. It does not universally prove selected-carrier possession.

What does received at Ponto Parceiro mean?

The parcel entered the posting-point network. Wait for carrier collection for stronger carrier custody evidence.

Does entered point distribution centre mean the carrier has it?

Not necessarily. It can still be moving within the partner-point network.

What proves the carrier has the parcel?

A carrier-collected, posted, received or accepted event from the selected carrier is stronger evidence.

Why is the carrier tracking code missing after posting?

Official webhook guidance says it can take up to one business day after posting, depending on the carrier.

Why can the label still show Released after posting?

The platform lifecycle can lag. Preserve the posting receipt and ask Melhor Envio support to correct the record.

Is Melhor Rastreio live GPS?

No. It synchronizes recorded carrier events periodically.

How often does Melhor Rastreio update?

Current guidance says it queries immediately, then checks every two hours for 30 days.

Why is the carrier website newer?

The carrier can publish an event before the next Melhor Rastreio synchronization.

Does the event city mean the delivery city?

Not always. It can be the city of the carrier unit responsible for the event.

What does CTe emitido mean?

A freight document was issued. It does not prove physical movement.

Does Out for Delivery guarantee delivery today?

No. It records route activity.

What does buscas mean?

The carrier is searching for the shipment. It is not yet a confirmed loss.

Does a suspected theft or damage status mean compensation is approved?

No. Carrier investigation and claim treatment remain necessary.

Can I change the delivery address through 11Tracking?

No.

Can Melhor Envio suspend delivery?

It can relay a request. The carrier must accept and execute it.

Does suspension requested mean the parcel is returning?

No. Wait for physical return events.

Does return to sender mean the buyer was refunded?

No. The merchant controls the refund or replacement.

Does every shipment have signed proof of delivery?

No. Proof depends on carrier and service.

Can 11Tracking retrieve POD?

No.

Who opens a claim?

The sender usually opens treatment through Melhor Envio support because the sender holds the account, label and posting evidence.

Does a tracking incident start the reimbursement clock?

Not necessarily. The carrier may first need to confirm a qualifying occurrence.

Does Melhor Envio compensate every delay?

Current public guidance does not provide a general delay-indemnity workflow.

Does wallet credit mean the buyer was refunded?

No.

Can I track a shipment created outside Melhor Envio in Melhor Rastreio?

Current Help Centre guidance says no, even if the carrier itself is integrated.

Which carriers are currently integrated?

The July 2026 official list includes Azul Cargo Express, Buslog, Correios, Jadlog, J&T Express, LATAM Cargo, Loggi and Total Express. Verify the current official list because it can change.

Can 11Tracking ask for CPF or CNPJ?

No. Use the official carrier site if identity data is required.

Is Melhor Envio international?

Current platform guidance describes its carrier services as domestic within Brazil.

Can 11Tracking open a support ticket, file a claim or refund the buyer?

No.

Use USTracking as a platform and carrier companion

USTracking may help:

• display supported public events for the actual carrier;
• preserve Melhor Envio as platform context;
• identify the underlying carrier when verified;
• distinguish ORD from the carrier code;
• separate label lifecycle, Ponto Parceiro custody and carrier custody;
• preserve raw carrier wording;
• show a safe public ETA, location or proof indicator when returned.

It cannot:

• treat Melhor Envio as the physical carrier;
• accept every ORD or merchant order;
• access the Melhor Envio account;
• collect CPF or CNPJ;
• buy, print, cancel or correct a label;
• arrange posting or collection;
• change an address;
• request delivery suspension;
• contact a driver;
• retrieve private proof;
• open a support ticket;
• file a claim;
• approve indemnification;
• credit a wallet;
• refund the buyer;
• recover a parcel;
• guarantee delivery.

Use it to understand public evidence, then use Melhor Envio, the selected carrier, sender or merchant for action.

Scope, evidence and limitations

• Entity scope: Melhor Envio is a shipping and freight-intermediation platform, not a physical carrier.
• Transport scope: the selected carrier performs collection, movement, delivery, proof, incident analysis and return.
• Geographic scope: current official platform carrier guidance concerns domestic shipping within Brazil.
• Tracking scope: Melhor Rastreio supports currently integrated carriers and platform-generated shipments.
• Coverage limitation: a valid carrier code from an external shipment is not necessarily supported by Melhor Rastreio.
• Carrier-list limitation: the July 2026 list is dated and can change.
• Identifier scope: the carrier tracking code is the preferred public input.
• ORD limitation: ORD is generally an internal protocol; carrier-specific support such as the current Total Express flow must be verified rather than generalized.
• Order limitation: a merchant order number is not automatically a Melhor Envio or carrier tracking reference.
• Multi-parcel scope: one order can contain several parcels, carriers and tracking codes.
• Label limitation: created, paid, released, generated and printed labels do not prove physical handoff.
• Posting-point scope: Ponto Parceiro or Pegaki receipt proves entry into the point network, not selected-carrier collection.
• Custody scope: carrier-collected or explicit carrier-accepted evidence is stronger than platform lifecycle.
• Tracking-code limitation: the carrier code can appear after posting.
• Synchronization scope: current guidance describes an immediate query followed by two-hour checks for 30 days.
• Live-location limitation: neither Melhor Rastreio nor 11Tracking provides continuous GPS.
• Location limitation: the event city can identify the responsible carrier unit rather than the recipient city.
• Status limitation: normalized wording must not erase a material raw carrier instruction.
• CTe limitation: freight-document issuance does not prove movement.
• Delivery limitation: Out for Delivery does not guarantee completion that day.
• Incident limitation: searches, suspected loss, theft, damage or violation require later carrier analysis.
• Suspension limitation: a suspension request does not prove interception or return.
• Return limitation: reverse movement and sender receipt are separate.
• Proof scope: proof type and access depend on carrier, service and account workflow.
• Claim scope: loss, robbery, damage, insured value, deadlines and compensation are carrier-specific.
• Commercial scope: carrier indemnification, Melhor Envio wallet credit and buyer refund are separate.
• Privacy scope: CPF, CNPJ, addresses, invoices, declarations, values, payment, proof and claim data remain private.
• Runtime boundary: no generic Melhor Envio carrier lock is safe; the underlying carrier must be identified or tracking must decline.
• Last reviewed: July 29, 2026.
• Next scheduled review: October 27, 2026.

11Tracking is independent and is not Melhor Envio, LWSA, Melhor Rastreio, Ponto Parceiro, Pegaki, the selected carrier, the sender, merchant, recipient, marketplace, driver, support team, insurer or claims authority. It does not quote or buy freight, create or cancel labels, receive or transport parcels, arrange collection, change addresses, suspend delivery, create carrier scans, retrieve private proof, investigate incidents, approve claims, credit wallets, refund buyers, recover parcels or guarantee delivery.