Skip to main content

​
Marketplace checkout

​
Direct evidence

  • Vector router composition: vector/app/api/v1/routes.py.
  • Vector checkout/payment orchestration: vector/app/service/cart_orchestration_service.py, payment_service.py, and medusa_service.py.
  • Vector integration inventory: vector/README.md documents Medusa, Mint gRPC, Redis, SQS, SNS, short URLs, and Google Maps.
  • Mint starts HTTP routers plus embedded gRPC: mint/app/main.py.
  • Mint documents callbacks to Vector, Dermadesk, Orderbox, and Konsilo: mint/README.md.
  • Medusa cart completion and cart-to-order paths: medusa-store/src/api/store/carts/[cart_id]/complete-v2/route.ts and order/route.ts.
  • Orderbox integration clients: orderbox/app/clients/estimo_client.py and reservation_client.py.
  • Storehouse reservation services: storehouse/app/service/redis_reservation_service.py and reservation_service.py.
The end-to-end sequence shown after payment is a high-confidence integration inference based on direct downstream clients and documented callbacks. Trace IDs, runtime configuration, and actual queue payloads should be used to confirm any incident-specific path.

​
Product discovery

  1. Atlas publishes catalog-oriented APIs from atlas/app/api/v1/endpoints/ and derives commerce data through Medusa service modules.
  2. Compass exposes search/recommendation APIs at compass/app/api/v1/endpoints/ and app/api/v2/endpoints/; its clients include Atlas, Medusa, Redis, and Netcore.
  3. Tetris calls Strapi and Compass services to build CMS/recommendation responses: tetris/app/services/strapi_client.py, recs_service.py, and fill_service.py.

​
Consultation transaction

  1. Dermadesk owns booking, slot, consult-cart/order/payment, and prescription HTTP APIs in dermadesk/app/api/v1/.
  2. Dermadesk verifies Mint and Konsilo gRPC readiness in dermadesk/app/main.py.
  3. Konsilo exposes HTTP and gRPC from konsilo-be/src/main.ts, and owns clinical domain modules under konsilo-be/src/.
  4. Mint’s documented downstream callbacks include both Dermadesk and Konsilo.

​
Inventory and fulfilment

Storehouse receives inventory/product/order events, performs Redis-backed atomic reservations, persists inventory/audit data, and synchronizes platforms. This is evidenced by storehouse/app/main.py, worker_main.py, redis_reservation_service.py, and cross_platform_inventory_sync.py. Estimo reads warehouse availability and applies geographic/delivery-mode rules from estimo/app/service/delivery_service.py and pincode_service.py. Orderbox owns ERP payloads, shipment, and return service code under orderbox/app/service/v3/.