E-invoices
Issue MeInvoice automatically when Haravan orders meet rules.
sync_orders
API integration · Haravan → MeInvoice
Haravan shops need MeInvoice e-invoices when orders are placed — no manual copying. GenNova Dev creates invoices, updates status and lookup codes when conditions are met. On failure, the system logs and supports retry.
Haravan shops need MeInvoice e-invoices when orders are placed — no manual copying. GenNova Dev creates invoices, updates status and lookup codes when conditions are met. On failure, the system logs and supports retry.
Multi-entity businesses use Haravan → MeInvoice V2 (AIO): one shop connects to multiple MeInvoice accounts (multiple tax IDs), each with its own token and invoice templates. Set a default MST and assign MST per branch, sales channel or storefront via sub-mapping — ideal for groups, franchises or multi-brand shops.
Technical flow on GenNova Dev — from API connection to logging, based on the actual convert pipeline.
Issue MeInvoice automatically when Haravan orders meet rules.
sync_ordersRefresh MeInvoice RefID and update lookup code on Haravan orders.
refresh_meinvoice_statusSync catalog and buyers to MeInvoice (can reuse AMIS cache).
sync_productssync_customersYes. When an order meets configured conditions, the system issues an e-invoice and updates the lookup code.
Detailed logs per order, manual or bulk retry support and alerts on failure.
V2 uses the new MeInvoice API with draft → publish on one platform, better logs and retries.
Configurable by order type; conditions set in the MeInvoice dashboard.
Not required for e-invoice issuance; product/customer cache from AMIS can be used if connected.
Yes — via Haravan → MeInvoice V2 (AIO). Add multiple MeInvoice accounts (one MST per row), set a default MST and assign MST per branch / channel / storefront through sub-mapping.