Appearance
Amazon
Amazon is represented as a marketplace channel behind connector accounts such as Shoppingfeed or Lengow. The reviewed Logidav source proves connector order and shipment paths; it does not prove that every Amazon catalog, stock, or price field is currently published.
Evidence boundary
This page describes source at commit 42116ebc0ba509bce9cc6651a55ecefd9a5fdb38. Amazon account ownership, connector configuration, schedules, feed acceptance, and Amazon readback remain runtime questions.
Components
| Component | Source-backed role |
|---|---|
| Shoppingfeed | Imports unacknowledged connector orders and can post acceptance/acknowledgement and shipment feedback. The source currently contains a debug stop before Shoppingfeed order persistence; see Shoppingfeed. |
| Lengow V3 | Imports orders for configured marketplace accounts and stores marketplace/account metadata on the sale; shipment/action feedback is handled by the service. See Lengow. |
| Amazon | Provider endpoint/channel whose active account and catalog contract must be verified outside the reviewed Logidav source. |
Data flow
- Amazon activity is received by the configured connector.
- A connector-specific command maps provider orders into Logidav
SaleandSaleProductrecords. - Shipment events can send tracking/action feedback through the connector service.
- Catalog, stock, and price publication is only documented when a connector-specific source path and runtime readback are available.
Order import
Use the connector page for exact commands and account identifiers. Do not invent an amazon:* Logidav command: the reviewed source uses Shoppingfeed and Lengow entry points instead. Each connector has its own import guard, deduplication key, status mapping, and provider acknowledgement behavior.
Catalog synchronization
The existence of an Amazon channel does not establish that Logidav publishes titles, descriptions, images, attributes, prices, or stock directly to Amazon. Confirm the active connector feed/export, mapping rules, successful provider response, and marketplace readback before documenting a field as synced.
Error handling
Treat connector failures, provider rejection, missing product mappings, and unacknowledged orders according to the connector’s own evidence and runbook. A successful local command or generated feed is not proof that Amazon accepted the change.