Appearance
Shared Business Flows
These pages trace business outcomes across system boundaries. Each separates what a cited source proves from a documented relationship, a missing segment, and the behavior that still needs review. Read the evidence boundary before treating a diagram as the deployed path.
Priority journeys
| Flow | Current evidence | Start here for |
|---|---|---|
| Central Meduse to Mosaikasa and Shopify | Source-traced targeted sync at a recorded Meduse revision; deployed configuration and current product state remain unverified. | Understanding which existing product changes are eligible, how they reach the tenant and Shopify, and where to diagnose a failure. |
| Product creation to storefront | Source-traced Logidav publication, Meduse jobs, Magento file imports and the return acknowledgement; runtime configuration and storefront acceptance remain unverified. | Following a new SKU from the Publish action through every file and consumer. |
| Partners and Lengow product feeds | Source-traced Partners and Magento selection rules, field sources, generation lifecycle and Lengow removal retention; deployed schedules and business-owner acceptance remain unverified. | Product-count, stock, price, promotion or availability differences between Partners and Lengow. |
| Order to delivery | Partial: Magento order import and CSV shipment creation are source-backed in Logidav; scheduler, some recovery behavior, carrier delivery, and customer tracking remain separate or unknown. | Order import gaps, shipment creation, or a difference between “shipped” and “delivered”. |
| Chatbot to business API | Partial: the Dify stream, conditional product-question cache path, and backend-to-Logidav SAV request are source-backed; the UI caller, configured base URL, and other downstream operations remain unknown. | Chat responses, optional product-answer caching, or the edge between the UI and a business API. |
| Stock and catalog | Partial: Logidav product import, quantity-log behavior, and the current queue-to-Magento API path have source refs; scheduler and marketplace propagation are not established. | Product availability/price disagreements, queue batches, or duplicate stock concerns. |
| Support and refunds | Partial: SAV creation and refund-check fragments are source-backed; a complete customer case/refund lifecycle and refund idempotency remain open. | SAV ticket creation, refund reconciliation, or a support case that spans several owners. |
Start from an application screen
- Logidav interfaces maps the menu builder to routes and the order, stock, marketplace, payment, support and administration workflows.
- Meduse interfaces maps Vue screens to API consumers. Follow Meduse workflows into the backend, connectors, scheduled jobs and queues.
- Menzzo Magento workflows identifies the storefront's source entry points, with a detailed catalog importer and catalog dependency consumers.
Menzzo commerce journeys
- Checkout and payment: from cart changes to provider callbacks and order state.
- Promotions and cart recovery: discounts, chatbot links, and distinct recovery flows.
- Product reservations: product form and OTP confirmation through Logidav import.
- Continue with Order to delivery and Support and refunds for operator changes, shipment feedback, cancellation and financial follow-up.
Meduse catalog journeys
These guides start at the application action and trace the data change through its processing and destination boundary:
- Product editing and spreadsheet bulk updates
- Attributes, families, categories and menus
- Images, files and Vimeo stories
- Logidav enrichment of the Mosaikasa catalog
- Family, attribute and ASIR mapping handoffs to Logidav
- Publication and connector handoffs, including a directory of earlier Meduse command notes
Still to map
Image-resizing ingestion/publication and review collection/moderation remain visible gaps in Documentation Coverage. The priority journeys do not make the rest of the ecosystem complete.
Evidence boundary
source-verified means the cited repository path was reviewed at the immutable commit named on that page. It does not establish which configuration is active, what is deployed, whether a scheduled command runs, what happened in production, or whether an owner accepted an end-to-end outcome. documented records a relationship from current docs; partial, unknown, and missing identify gaps explicitly.
Use Project Boundaries to locate the business owner, Repository Map to find canonical repository identities, and the coverage matrix for setup and operations gaps.