What LoloBuy’s official website actually confirms

LoloBuy’s public website is a working application rather than a conventional brochure. That makes the interface itself useful evidence—but only if route names, form fields and status labels are read as observations, not turned into promises the platform never made.

How this evidence was collected

We reviewed the production homepage and the routes, labels and form structures delivered by LoloBuy’s own current web application. The homepage identifies itself as release 1.0.1 and displays a build timestamp of 3 August 2026. On the review date, the application exposed public route definitions for freight estimation, product details, keyword and image search, manual ordering, order confirmation, stored items, rehearsal, parcel submission, order details and parcel details.

This method can confirm that a surface exists in the current build and can show what information the interface is designed to collect. It cannot tell us that every country, user, product or parcel will receive every option. Some controls are conditional, some commercial terms are transaction-specific and some answers appear only after the user enters a destination, item, weight or account-level information.

Route-level observation record

Some transaction routes can require sign-in or an eligible stored item before their full controls are visible. The evidence file records route definitions and interface structures delivered by the current production application; it does not claim that anonymous visitors can complete every workflow.

1. Product discovery and ordering are separate from fulfilment

The application contains product-detail, keyword-search, image-search and manual-order routes. The manual-order interface asks for more than a pasted URL: it includes a product title, specification or SKU, commodity price, domestic freight, quantity and supporting images, followed by add-to-cart or buy-now actions. That field structure tells us something practical. A source link identifies where an item was found, while the option, price and image identify what the buyer intends to request.

It would be wrong to convert the existence of this form into the claim that any Chinese marketplace item can always be purchased. Seller restrictions, unsupported goods, changed listings or platform-specific conditions can still intervene. The safe conclusion is narrower: LoloBuy provides structured ways to identify a product request, and users should review every generated order field before payment.

2. Order status labels describe domestic progress first

The current interface defines stages including pending payment, processing, ordering, shipped, arrived in warehouse, cancelled, returning, returned, submitted package and completed. These labels separate product acquisition from international parcel delivery. In particular, “shipped” in the product-order sequence describes movement toward the warehouse; it should not automatically be read as international dispatch to the buyer’s address.

The distinction matters for anyone starting from a spreadsheet. Paying for the product does not complete the international-shipping decision. Warehouse arrival creates a new decision point: confirm what arrived, inspect the evidence available for that stored item, resolve any important discrepancy and only then select items for a parcel.

3. Warehouse photos are evidence, not a blanket QC guarantee

LoloBuy’s current application contains a stored-items area, a quality-information component, normal-photo labels and an additional detailed or HD photo service surface. These elements support the statement that users can encounter warehouse-related visual evidence. They do not support the much stronger claim that every item is fully inspected against one universal checklist or that photographs prove authenticity, internal construction, electrical safety or durability.

A photograph is useful when the question is visible and specific: Does the colour broadly match? Is the selected label shown? Are both shoes present? Is the printed placement visibly skewed? It is much weaker for hidden materials or long-term performance. The honest editorial response is to ask what a particular image actually shows, then name what remains unobserved.

4. Freight estimates depend on parcel inputs

The estimate interface asks for destination, restriction information, warehouse choice, weight and package length, width and height. Its result structures can expose transit-time information, real versus volumetric weight, maximum-edge or combined-dimension limits, weight ranges and fees. This confirms that the route comparison depends on both where the parcel is going and what the packed parcel looks like.

It does not justify publishing a single permanent rate or volumetric divisor for “LoloBuy shipping.” A route can apply different charging logic or eligibility constraints, and available lines can change with destination, restricted contents and dimensions. The useful action is to enter the current parcel data and compare the actual result, not to force every shipment into an old formula copied from a forum post.

5. Rehearsal is pre-packing, not dispatch

The rehearsal interface describes a simulated pre-packing step. It can produce packed weight and dimensions before the user proceeds to a real parcel. This is especially useful when consolidation or protective packaging may materially change the route comparison. It is also easy to misunderstand: a rehearsal result is not an international shipment, does not create tracking and does not override route restrictions.

The correct sequence is to resolve product-level questions first, then use rehearsal when a more concrete packed size would improve the shipping decision. After that, the real parcel still requires its own review and submission.

6. Parcel submission combines address, route and customs decisions

The submit-parcel flow contains address and product information, packaging and value-added service choices, route selection, declaration currency and method, English declaration item names, quantities, weights and declared costs. Fee-detail structures can conditionally include shipping, first- and continued-weight charges, customs-related charges, fuel, service or operation fees, value-added services, tax and discounts.

The word “conditionally” is essential. Seeing a charge label in application code does not mean it appears on every parcel. The transaction-specific review should answer three questions: Is the address correct? Is the chosen line eligible for these items and dimensions? Do the declaration and fee breakdown accurately describe what is being submitted?

What the current official application supports—and what it does not

Notices that deserve real attention

The current application includes route notices warning that some lines may not offer overseas redelivery or return and advising users to monitor logistics and contact support when tracking becomes abnormal. It also presents customs and tax risk notices. These are not reasons to assume a bad outcome; they are reasons to read the selected line’s live terms instead of applying another route’s experience to the current parcel.

For the same reason, this evidence file does not publish a universal storage duration, insurance promise, compensation amount, refund policy or return window. Those claims require a stable, current official statement tied to the relevant scenario. If the answer is shown only inside a specific order or parcel, the user should rely on that live transaction record.

A practical reader checklist

1. Use LoloBuy’s live order fields to confirm the exact item, option, price and domestic freight.
2. Follow the product status until warehouse arrival; do not confuse domestic shipment with international dispatch.
3. Judge warehouse photos only against visible, category-specific questions.
4. Enter current destination, weight, dimensions and restrictions before comparing routes.
5. Use rehearsal as a packing estimate when dimensions matter, not as proof that a parcel has shipped.
6. Review the address, declaration, line notices and component charges immediately before parcel submission.