Appearance
Notio
Notio is a supplier feed and order-file integration. Product mapping supplies catalog fields, while order fulfillment is exchanged as JSON files over FTP.
Evidence boundary
This page describes source at commit 42116ebc0ba509bce9cc6651a55ecefd9a5fdb38. The feed URL, FTP account, schedules, and downstream acknowledgement state require runtime verification.
Entry points
| Operation | Command or service | Source behavior |
|---|---|---|
| Stock feed | menzzo:notio:sync-product-stock | Reads an XML feed, resolves noti-prefixed SKUs, updates quantity/active state, and batches product API updates. Products missing from the feed are set to quantity zero. |
| Product text | menzzo:notio:generate-notio-product-title-and-description | Generates title and description data for Notio products. Translation and dimension updates have separate commands. |
| Order export | menzzo:notio:generate-order-file | Creates one JSON payload per eligible sale line, uploads the order file to FTP, and marks the sale product as sent. |
| Export history | menzzo:notio:export-all-sales | Exports Notio sales for an operational/reporting path; exact schedule is not established by the reviewed source. |
Catalog mapping
NotioProductService::getMappingData() maps category, attribute, color, material, dimensions, parcel information, price, images, and drop_ship = "Notio". It also calculates shipping data using the supplier’s GLS/monocolis rules. The source confirms the local mapping payload; it does not prove that every mapped field is accepted by each downstream catalog.
Stock behavior and source discrepancy
The stock command processes the XML quantity and derives a status intended to be active above a quantity threshold. In the reviewed source, a later assignment resets that status to 0 before processProduct() is called. This is a source-level discrepancy, not a documented business rule; verify the deployed revision and add a decision before relying on the feed to activate products.
Two SKUs are explicitly forced inactive, and labels containing prob are treated as problematic. Products with drop_ship = 'Notio' that are absent from the feed are set to zero quantity. The command updates the local product/API visibility according to the calculated status.
Order-file behavior
The order export writes the sale increment id, supplier SKU, quantity, wholesale price, PDF shipping-label URL, and carrier into the JSON payload. The source maps CHRONOPOST separately and otherwise passes the carrier value from the sale data. It uploads through the configured FTP connector and updates the sale-product sent flag; FTP acceptance and provider processing are not verified by static source review.
What remains unknown
- The current XML feed contents and whether the status-reset behavior is present in production.
- The acknowledgement/prepared/shipped commands and their deployed schedule.
- Whether FTP upload success means Notio has accepted the order.
Source locations
src/NotioBundle/Services/NotioProductService.php— field mapping, image, price, and shipping payloads.src/NotioBundle/Command/SyncStockCommand.php— feed status and quantity behavior.src/NotioBundle/Command/Sale/Expedition/GenerateNotioOrderFileCommand.php— order-file construction and upload.