Appearance
Temu
Temu has source-backed product, stock, price, order-import, and shipment-confirmation paths. The product and price commands make provider writes; neither command is a dry run.
Evidence boundary
This page describes source at commit 42116ebc0ba509bce9cc6651a55ecefd9a5fdb38. Temu credentials, category mappings, schedules, and provider readback are not established by static review.
Entry points
| Operation | Command | Source behavior |
|---|---|---|
| Order import | menzzo:temu:import-orders | Paginates Temu orders, fetches details/shipping/amounts, maps items by extCode, and creates Logidav sales with increment ids prefixed Temu-. Existing increments are skipped. |
| Product sync | menzzo:temu:sync-products [update] [complianceEdit] | Iterates a hardcoded list of Temu category ids and syncs active/visible products. update enables existing-product updates; compliance editing accepts the source-supported compliance modes. |
| Stock push | temu:stock:update | Updates category stocks and prints OK/KO counts, returning failure when any item fails. |
| Price push | temu:price:update | Finds products with a Temu goods id, pushes price data, and reports per-goods-id success/failure. |
Additional category/specification commands populate or inspect Temu mappings. They should be treated as preparation steps, not as a product sync substitute.
Product mapping
TemuProductMapper reads store-3 price, special-price dates, and shipping amount. It builds Temu goods/SKU data, category properties, images, and bullet descriptions. The source applies a marketplace amount calculation (price + shipping) * 0.8; verify the business rule before changing it. Product sync also has compliance payloads for manufacturer/responsible-party/certificate flows.
Order mapping and shipment confirmation
Order import uses Temu’s retail VAT-inclusive amount when available and falls back to local product plus shipping. It maps shipping contact/address fields and the parent order status into Logidav states. The service stores the raw Temu order payload in sale order information.
When Temu shipments are printed, the service groups Temu sale products, requires a supported carrier and tracking number, and confirms the shipment with the Temu API. Missing tracking data produces a failure notification rather than a provider confirmation.
What remains unknown
- Whether all hardcoded category ids are still valid and intentionally in scope.
- Which compliance mode values are accepted by the deployed command; the help text and validation are not fully aligned.
- Whether stock/price/product responses are persisted and monitored beyond command output.
- Whether an external catalog feed also publishes Temu data.
Source locations
src/ErpBundle/Command/Temu/— product, stock, price, and order command entry points.src/ErpBundle/Services/Temu/TemuService.php— order mapping, stock updates, and shipment confirmation.src/ErpBundle/Services/Temu/TemuProductMapper.php— product/price payload construction.