Channable

Channable is an order-import and shipment-feedback connector in the reviewed source. No product-catalog publishing command was found in this source pair.

Evidence boundary

This page describes source at commit 42116ebc0ba509bce9cc6651a55ecefd9a5fdb38. It does not prove that the Channable project/company ids, API URLs, token, or schedules are current.

Entry points

Operation	Command or event	Source behavior
Order import	channable:sales:import	Imports orders with status not_shipped from two days ago, maps products by reference/SKU, and creates Logidav sales unless the import guard is disabled.
Shipment feedback	SaleProductsShippedEvent	For Channable sales with a tracking id, posts order-item ids, tracking code, and transporter to Channable.
Cancellation feedback	Channable sale cancellation event	Posts cancellation data to the configured Channable API path.

The command reads project_id, company_id, api_url, v1_api_url, and the source key spelled acess_token from the channable parameter block. Preserve that spelling when verifying the existing deployment, but do not copy credentials into documentation.

Order mapping rules

The command returns without writing when mz.sale->canImportSales() is false. The service skips orders already represented by the Channable source and skips unpaid orders. Product lines are resolved by reference code/SKU. A default customer-availability option is attached with a calculated delivery date; the source maps Channable order statuses into Logidav sale states and stores the raw Channable order information for later shipment updates.

Shipment rules

Shipment feedback uses the V1 endpoint:

{v1_api_url}companies/{company_id}/projects/{project_id}/orders/{sale_id}/shipment

The transporter mapping recognizes Chronopost, GLS, and other supported carrier names; the source default is GEODIS. If order-item ids or tracking are missing, the service skips the outbound update. Exceptions are logged/dumped by the reviewed source and are not rethrown from the event handler.

What remains unknown

• Whether product feeds are published to Channable by another application.
• Whether the hardcoded two-day import window is sufficient for recovery.
• Whether shipment and cancellation responses are persisted or monitored.
• Which deployment contains the current configuration key spelling.

Source locations

• src/ErpBundle/Command/Channable/ImportChannableSalesCommand.php — import guard, date/status window, and configuration.
• src/ErpBundle/Services/Channable/ChannableService.php — order mapping, shipment endpoint, carrier mapping, and cancellation callback.