E-Commerce · Beta
EasyEcom
API integration
Ship E-Commerce features without building the integration. Full EasyEcom API access via Proxy and 90+ MCP-ready tools for AI agents — extend models and mappings to fit your product.
Built for specific customer use cases. Issues are resolved quickly.
Talk to usUse Cases
Why integrate with EasyEcom
Common scenarios for SaaS companies building EasyEcom integrations for their customers.
Embed OMS/WMS visibility into post-purchase CX
Post-purchase and helpdesk SaaS platforms can offer EasyEcom as a native connector so their users see real warehouse and shipping status—not just storefront events—and can fix pre-dispatch issues like wrong pin codes directly from the support UI.
Power branded returns portals with warehouse-grade QC
Returns management SaaS can let merchants trigger reverse pickups, track pending returns, and gate refunds on actual warehouse QC confirmation, closing the loop between the shopper-facing portal and the WMS.
Feed demand planning and BI tools with operational data
Forecasting and BI products can ingest inventory snapshots, purchase orders, GRNs, and async bulk reports from EasyEcom to predict stockouts, flag expiring inventory, and auto-draft replenishment POs for FMCG and CPG brands.
Launch a B2B wholesale ordering layer on top of EasyEcom
B2B commerce and distributor portal SaaS can create customers, place B2B orders, and generate tax-compliant B2B invoices through a single integration—giving wholesalers a native EasyEcom-backed checkout.
Bridge e-commerce fulfillment with ERP ledgers
ERP and accounting connectors can write back sales order and credit note ERP statuses to EasyEcom while pulling B2B invoices and payment details, keeping fulfillment and finance systems reconciled without custom glue code.
What You Can Build
Ship these features with Truto + EasyEcom
Concrete product features your team can ship faster by leveraging Truto’s EasyEcom integration instead of building from scratch.
Real-time shipment milestone sync
Pull carrier-level tracking details by AWB from EasyEcom to drive proactive delay alerts, ETA predictions, and status timelines inside your product.
Pre-dispatch order editing
Let support agents or shoppers update shipping addresses and cancel or rename orders before dispatch to cut down on RTOs and failed deliveries.
Reverse pickup and RMA orchestration
Initiate returns with parent SKU and reason, monitor pending return status, and trigger refund workflows once warehouse QC confirmation lands.
Automated PO drafting from stock signals
Combine inventory snapshots, expiry reports, GRNs, and open purchase orders to auto-generate replenishment POs when stockouts or dead stock are predicted.
Unified B2B + B2C order creation
Expose a single order creation flow in your app that routes B2C, B2B, and stock-transfer orders into EasyEcom with the correct order type and generates B2B invoices on demand.
Async bulk reporting pipeline
Queue inventory, sales, and expiry reports, poll for completion, and stream the downloads into your data warehouse without worrying about pagination limits.
SuperAI
EasyEcom AI agent tools
Comprehensive AI agent toolset with fine-grained control. Integrates with MCP clients like Cursor and Claude, or frameworks like LangChain.
create_a_easy_ecom_access_token
Get an API JWT (valid 90 days) with the stored email, password and location key. The connector does this on connect and every week; you rarely need it directly.
create_a_easy_ecom_asn
Create ASN. Required: vendor_token, po_id, asn_details.
create_a_easy_ecom_b_2_b_invoice_detail
This API is used to update invoice details for an order in OMS. Required: invoice_id, base64url.
create_a_easy_ecom_b_2_b_invoice
It is used to generate a B2B invoice. Required: invoiceId.
create_a_easy_ecom_b_2_b_order_approval
This API is used to approve B2B orders, similar to the approval process available in the EasyEcom UI: Orders → B2B Orders → Unapproved Orders → Approve Order . Required: reference_code, sku, confirmedQuantity.
create_a_easy_ecom_b_2_b_order_assignment
This API is used to assign inventory to the respective SKU/order via API. Required: order_items, suborder_num, quantity, sku, items.
create_a_easy_ecom_b_2_b_tracking_status
Updates the tracking/shipping status of a B2B order (AWB). Required Fields.
create_a_easy_ecom_batch_inventory_update
This Asynchronous API is used to update/overwrite the EasyEcom inventory for the mentioned SKUs with batch code and expiry. Please note: This API only works for the Non-WMS plan . Required: sku, quantity, batchCode.
create_a_easy_ecom_bulk_inventory_update
This Asynchronous API is used to update/overwrite the EasyEcom inventory for the mentioned SKUs. Please note: This API only works for the Non-WMS plan . Required: sku, quantity.
create_a_easy_ecom_business_order
We have one API to create multiple types of orders as below : B2C - B2C stands for Business-to-Consumer, a model where businesses sell products or services directly to individual consumers. Required: orderType, orderNumber, orderDate, is_market_shipped, OrderItemId, sku, ean, AccountingSku, Quantity, Price, marketplace_id, paymentMode, shippingMethod.
create_a_easy_ecom_carrier_credential
It is used to integrate the carrier with Easyecom. NOTE:-Refer our Knowledgebase, which is given below, to know which field is required and it varies with carriers and aggregators. Knowledgebase URL- https://support.easyecom.io/portal/en/kb/campaigngroup1450092794169. Required: carrier_id, username, password.
create_a_easy_ecom_carrier_estimated_delivery_date
It is used to get Estimated delivery date. EasyEcom Internally calls carrier APIs to fetch the Estimate delivery date. Required: SKU, drop_pincode.
create_a_easy_ecom_carrier_reassignment
Reassign Carrier. Required: company_carrier_id. Note: this GET changes data in EasyEcom.
create_a_easy_ecom_carrier_unassignment
It is used to Un-assigning the carrier. Required: invoice_id.
list_all_easy_ecom_channel_statuses
This API returns the list of marketplaces that have been integrated in the location, along with the status of the integrated marketplaces. The following information can be retrieved; Marketplace Name Marketplace ID Status = Active/Inactive.
list_all_easy_ecom_child_locations
The authentication token is an alphanumeric code, unique to your Easyecom account, can be used from any system to validate your API calls to access Easyecom resources. Easyecom API uses JWT tokens for validation. Use this API to validate your API user and obtain the authentication token. Required: email, password, location_key.
list_all_easy_ecom_company_attributes
Returns the payment or delivery term names and code which will be useful in other API calls. Required: type.
list_all_easy_ecom_company_groups
Returns the invoice or pricing group values and code which will be useful in other API calls. Required: type.
create_a_easy_ecom_consolidated_inventory_report
Steps to Generate the Report: Queue the Report Request Initiate the process by queuing the required report using the respective available Queue Report API. Capture the reportId Upon a successful request, you will receive a response containing a unique reportId . Required: api_token, reportType, invoiceType, warehouseIds, dateType, startDate, endDate.
list_all_easy_ecom_countries
It is used to get country details.
create_a_easy_ecom_credit_note_erp_status
It is used to update the Sales ERP transaction ID (Invoice no. of ERP) in EasyEcom. Required: items, credit_note_id, erp_status_id, erp_transaction_id, erp_response.
list_all_easy_ecom_custom_fields
It return the custom fields from account. Required: type.
create_a_easy_ecom_customer
It is used to create a Wholesale(B2B) customer in the account. Required: companyName, email, password, country, billingStateId, billingPostalCode, currency, dispatchStateId, taxIdentificationNumber.
list_all_easy_ecom_customers
It is used to get all customer details that are available in the account. Required: type.
update_a_easy_ecom_customer_by_id
It is used to update wholesale customer details and in response customer_id will be returned. Required: id.
create_a_easy_ecom_estimated_delivery_date
It is used to get Estimated delivery date. EasyEcom Internally calls carrier APIs to fetch the Estimate delivery date. Required: SKU, drop_pincode.
list_all_easy_ecom_grn_statuses
It is used to create an Auto GRN in EasyEcom. Required: vendor_id, sku, quantity, cost, queue_id.
list_all_easy_ecom_grns
It returns the created GRN along with details between the given date range. Note:- If none of the optional parameters are passed, by default last 7 days of GRN data will be received in the Response according to the GRN created date. The connector follows nextUrl through every page.
create_a_easy_ecom_grn
It is used to create an Auto GRN in EasyEcom. Required: vendor_id, sku, quantity, cost, queue_id.
create_a_easy_ecom_inventory
This API is used to update/overwrite the EasyEcom inventory one SKU at a time. Please note: This API only works for the Non-WMS plan . Required: company_product_id, sku, quantity.
list_all_easy_ecom_inventory
It is used to get inventory details. Required: includeLocations. The connector follows nextUrl through every page.
create_a_easy_ecom_inventory_hold
The Given API is used to update Hold Inventory. The Hold qty will be deducted while the inventory is pushed to Marketplace channels. Required: sku, location_key, hold_qty.
list_all_easy_ecom_inventory_serials
It is used to fetch inventory along with the serial number if available. Required: sku, status.
list_all_easy_ecom_inventory_snapshots
It is used to get an Inventory Snapshot. Required: start_date, end_date.
create_a_easy_ecom_kit
It is used to create a Kit product, and the product ID will be generated in the successful response. Required: Sku, subProducts, sku, quantity.
list_all_easy_ecom_kits
It is used to get all Kit Products.
list_all_easy_ecom_listing_imports
It is used to import the listings for the selected marketplace/channel. Required: marketplaceId. Note: this GET changes data in EasyEcom.
create_a_easy_ecom_listing_mapping
It is used to map the channel listings with the master SKU in EasyEcom. Required: channelId, identifier, masterSku.
create_a_easy_ecom_listing
It is used to create listings in EasyEcom. Required: marketplaceId, sku, listingRefNum, guid, mrp, identifier.
list_all_easy_ecom_locations
It is used to get all locations against the primary location.
create_a_easy_ecom_manifest_document
It is used to update the external manifest document against a specific manifest number. Required: manifest_number, manifest_url.
create_a_easy_ecom_manifest
It is used to create Manifest. Required: carrier_id, marketplace_id, awb_numbers.
create_a_easy_ecom_marketplace_listing
This API is used to create the channel listings against any specific marketplace channel and map it against the master SKU. Please Note: Maximum number of supported listing values in a single API call: 20 Currently only supported for the given marketplaces: Flipkart Amazon Myntra PPMP Amazon Smart Connect. Required: marketplaceId, sku, mpSku, mpProductId.
easy_ecom_marketplace_listings_search
Returns the Marketplace listings. If MasterSKu is not present, then the listing is not mapped to any master. Keep increasing the page number till it gives an empty array to get all the listings. Page size increment is not recommended. Required: marketPlaceID.
list_all_easy_ecom_marketplaces
It is used to get all marketplace list of Easyecom.
create_a_easy_ecom_order_address_update
It is used to update billing and shipping address to pending and assigned order status. Required: order_id, shipping_pin_code.
create_a_easy_ecom_order_cancel_rename
This is for cancelling order and renaming it, in order to create a new order with same name as previous order. Required: Invoices, Rename.
create_a_easy_ecom_order_cancellation
It is used to cancel an order. The following parameters can be used to process the cancellation. Required: reference_code, invoice_id, suborder_num, m_id.
create_a_easy_ecom_order_confirmation
This API is used to confirm the order in Easyecom, and it returns the order ID or invoice ID in the successful response. The Invoice ID parameter is generally used when the order is a split order. In this case, the order ID is the same for the two different orders. Required: x-api-key, Authorization.
list_all_easy_ecom_order_counts
It is used to get the order count in the given date range.
list_all_easy_ecom_order_details
It is used to get order details against the particular order number. Note:- It works only for a single order. Required: reference_code, order_id, invoice_id.
list_all_easy_ecom_order_documents
It is used to get the documents(Invoice & label) using the invoice ID. Required: invoice_id, is_api.
create_a_easy_ecom_order_inventory_assignment
This API is used when inventory is in an “Unassigned Inventory” state for any SKU/order to assign inventory to the respective SKU/order. Required: order_items, suborder_num, quantity, sku.
create_a_easy_ecom_order_qc_confirmation
It is used to pass the QC using the invoice ID. Required: invoice_id.
create_a_easy_ecom_order_tag_loop
Tag Loop.
create_a_easy_ecom_order
We have one API to create multiple types of orders as below : B2C - B2C stands for Business-to-Consumer, a model where businesses sell products or services directly to individual consumers. Required: orderType, orderNumber, orderDate, is_market_shipped, OrderItemId, sku, ean, AccountingSku, Quantity, Price, marketplace_id, paymentMode, shippingMethod. One endpoint for B2C, B2B and stock-transfer orders (orderType).
list_all_easy_ecom_orders
The Orders API enables you to retrieve all types of orders, including B2B, B2C, and STN orders. The API returns a JSON response with comprehensive details for each order. Features Retrieve all orders associated with the account. Apply filters to narrow results by specific criteria. The connector follows nextUrl through every page.
list_all_easy_ecom_payment_details
It is used to get payment details against particular payment id. Required: payment_id.
list_all_easy_ecom_payments
It is used to get payment data. NOTE:- If "payment_start_date" is passed, then it's mandatory to pass "payment_end_date" parameter and vice versa. The connector follows nextUrl through every page.
list_all_easy_ecom_pending_returns
It is used to get all pending return order details. Note:- If none of the optional parameters are passed, by default last 7 days of pending return data will be received in the Response according to the pending return date. The Maximum date range allowed between the created_before and created_after in the API is 7 Days. The connector follows nextUrl through every page.
create_a_easy_ecom_pending_return
It is used to mark the order as pending return. Required: reference_code, parent_sku, child_sku, initiated_return_date, return_reason, return_quantity, return_type, return_awb, return_carrier_name.
easy_ecom_pending_returns_cancel
This is to enable cancellation of pending returns, when the courier partner cancels the AWB and a new one must be assigned. Required: creditNoteId.
list_all_easy_ecom_product_counts
It is used to get the count of all master products for the location.
create_a_easy_ecom_product_status
It is used to activate and deactivate the product. Required: status, product_id.
list_all_easy_ecom_products
It is used to get all the master products according to location. The connector follows nextUrl through every page.
create_a_easy_ecom_product
It is used to create products, and on a successful response, "product_id" will be returned. Note: We have to use either shelf life or shelf life percentage while creating products. Required: Brand, Sku, Category, ModelNumber, Cost, Weight, Length, Height, Width, TaxRate, materialType.
update_a_easy_ecom_product_by_id
It is used to update the details of the product. Note: We have to use Either shelf life or shelf life percentage while creating products. Required: id, sku, external_product_id.
create_a_easy_ecom_purchase_order_status
Update PO Status. Required: po_id, po_status.
list_all_easy_ecom_purchase_orders
It returns the purchase order for the given date range. Note:- If none of the optional parameters are passed, by default last 7 days of PO data will be received in the Response according to the purchase order created date. The connector follows nextUrl through every page.
create_a_easy_ecom_purchase_order
It is used to create a Purchase order, and the purchase order ID will be obtained in the successful response. Note:- Optional parameter keys should be present in the JSON body, but can be left blank. By default, the status of the Purchase order will be "Waiting for Approval". Required: vendorId, sku, ean, AccountingSku, quantity, unitPrice, referenceCode, createOrUpdate.
list_all_easy_ecom_queue_statuses
We can check the queue status of B2B Generate Invoice. NOTE:- Only if "message": "Finished" in api response, you can download the invoice using the URL provided in the result key. Required: queueId.
list_all_easy_ecom_report_downloads
It's a Dowload Reports. Required: api_token, reportId.
create_a_easy_ecom_report
Steps to Generate the Report: Queue the Report Request Initiate the process by queuing the required report using the respective available Queue Report API. Capture the reportId Upon a successful request, you will receive a response containing a unique reportId . Required: api_token, reportType, invoiceType, warehouseIds, dateType, startDate, endDate. Report types in the docs: FULL_INVENTORY_REPORT, GRN_DETAILS_REPORT, INITIATED_RETURN_REPORT, INVENTORY_AGING_REPORT, INVENTORY_EXPIRY_REPORT, INVENTORY_VIEW_BY_BIN_REPORT, MINI_SALES_REPORT, PENDING_RETURN_REPORT, PICKER_PACKER_REPORT, PUTAWAY_REPORT, QC_REPORT, RETURN_REPORT, SERIAL_OUT_OF_SYSTEM_REPORT, STATUS_WISE_STOCK_REPORT, TAX_REPORT. Then poll reports.list and download with report_downloads.list.
list_all_easy_ecom_reports
It's a List report we have to verify the report status. Required: api_token.
list_all_easy_ecom_return_details
It is used to get return details against the particular order number with the breakup types. Note:- It works only for a single order. Required: reference_code, order_id, invoice_id, credit_note_id.
create_a_easy_ecom_return_initiation
This API is used to initiate RVP against any forward order. Please note: The account should be enabled with a Reverse carrier for this API. Required: reference_code, parent_sku, child_sku, return_reason, return_quantity.
delete_a_easy_ecom_return_initiation_by_id
Delete Initiated return. Required: id. EasyEcom's docs show this call on the staging host; the connector sends it to api.easyecom.io.
create_a_easy_ecom_return
It is used to mark a return to the order. Required: order_id, invoice_id, items, sku, quantity.
list_all_easy_ecom_returns
It is used to get all the returned order details data. Note:- If none of the optional parameters are passed, by default last 7 days of returned data will be received in the Response according to the returned date. The connector follows nextUrl through every page.
create_a_easy_ecom_sales_order_erp_status
It is used to update the Sales ERP transaction ID (Invoice no. of ERP) in EasyEcom. Required: items, invoice_id, erp_status_id, erp_transaction_id, erp_response.
create_a_easy_ecom_shipment_assignment
Assign Shipment Details. Required: invoiceId, courier, awbNum, companyCarrierId.
create_a_easy_ecom_sku_price
It is used to insert the pricing of the SKU. Required: priceGroupId, sku, minQty, maxQty, price.
list_all_easy_ecom_states
It is used to get states of country. Required: countryId.
list_all_easy_ecom_tracking_details
It is used to fetch current tracking status and tracking history. Required: reference_code, awb_number, return_awb_number.
create_a_easy_ecom_tracking_status
It is used to update the tracking Status. Required: current_shipment_status_id, awb.
list_all_easy_ecom_users
It is used to get user details of account. Required: id, email.
create_a_easy_ecom_vendor
It is used to create vendors with the associated api_token, and "vendor_id "will be returned in the Successful response. Required: emailId, state, country, currency, zip, taxIdentificationNumber, PAN.
list_all_easy_ecom_vendors
It is used to get vendor details. The connector follows nextUrl through every page.
update_a_easy_ecom_vendor_by_id
It is used to update vendor details. Required: id.
create_a_easy_ecom_virtual_inventory
It is used to update the Virtual inventory. NOTE: To use this function, make sure your account's virtual inventory is enabled. If it isn't, get in touch with customer support:- care@easyecom.io. Required: sku, virtual_invent_count.
Why Truto
Why use Truto’s MCP server for EasyEcom
Other MCP servers give you a static tool list for one app. Truto gives you a managed, multi-tenant MCP infrastructure across 1050+ integrations.
Auto-generated, always up to date
Tools are dynamically generated from curated documentation — not hand-coded. As integrations evolve, tools stay current without manual maintenance.
Fine-grained access control
Scope each MCP server to read-only, write-only, specific methods, or tagged tool groups. Expose only what your AI agent needs — nothing more.
Multi-tenant by design
Each MCP server is scoped to a single connected account with its own credentials. The URL itself is the auth token — no shared secrets, no credential leaking across tenants.
Works with every MCP client
Standard JSON-RPC 2.0 protocol. Paste the URL into Claude, ChatGPT, Cursor, or any MCP-compatible agent framework — tools are discovered automatically.
Built-in auth, rate limits, and error handling
Tool calls execute through Truto’s proxy layer with automatic OAuth refresh, rate-limit handling, and normalized error responses. No raw API plumbing in your agent.
Expiring and auditable servers
Create time-limited MCP servers for contractors or automated workflows. Optional dual-auth requires both the URL and a Truto API token for high-security environments.
How It Works
From zero to integrated
Start with EasyEcom in a free sandbox, usually ready within one business day. No boilerplate, no maintenance burden.
Link your customer’s EasyEcom account
Use Truto’s frontend SDK to connect your customer’s EasyEcom account. We handle all OAuth and API key flows — you don’t need to create the OAuth app.
We handle authentication
Don’t spend time refreshing access tokens or figuring out secure storage. We handle it and inject credentials into every API request.
Call our API, we call EasyEcom
Truto’s Proxy API is a 1-to-1 mapping of the EasyEcom API. You call us, we call EasyEcom, and pass the response back in the same cycle.
Unified response format
Every response follows a single format across all integrations. We translate EasyEcom’s pagination into unified cursor-based pagination. Data is always in the result attribute.
FAQs
Common questions about EasyEcom on Truto
Authentication, rate limits, data freshness, and everything else you need to know before you integrate.
How does authentication to EasyEcom work through Truto?
EasyEcom uses a token-based auth flow. Truto handles the access token lifecycle via the create_a_easy_ecom_access_token call and attaches credentials to every downstream request, so your end users only connect their EasyEcom account once.
Do we need to handle EasyEcom's nextUrl pagination ourselves?
No. Truto abstracts EasyEcom's nextUrl cursor logic and automatically paginates through list endpoints like list_all_easy_ecom_inventory, list_all_easy_ecom_orders, and list_all_easy_ecom_returns so you receive complete datasets.
How fresh is the inventory and order data?
EasyEcom is designed for sub-60-second inventory sync across channels. Through Truto you can poll list endpoints or trigger reports on demand to get near real-time stock, order, and tracking state.
Can we create B2B orders and invoices, not just B2C?
Yes. create_a_easy_ecom_order supports B2C, B2B, and stock transfer flows via the orderType parameter, and B2B tax invoices can be generated using create_a_easy_ecom_b_2_b_invoice and create_a_easy_ecom_b_2_b_invoice_detail.
How do we extract large historical datasets without hitting rate limits?
Use the async reporting pattern: call create_a_easy_ecom_report for types like FULL_INVENTORY_REPORT or MINI_SALES_REPORT, poll list_all_easy_ecom_reports for completion, and fetch the file via list_all_easy_ecom_report_downloads.
Can we write accounting data back into EasyEcom from an ERP?
Yes. ERP integrations can push transaction status back using create_a_easy_ecom_sales_order_erp_status and create_a_easy_ecom_credit_note_erp_status, enabling true two-way sync between EasyEcom and the finance system.
Does the integration support custom fields?
Yes. You can retrieve tenant-defined fields via list_all_easy_ecom_custom_fields and map them into your product's schema so merchant-specific attributes flow through end to end.
From the Blog
EasyEcom integration guides
Deep dives, architecture guides, and practical tutorials for building EasyEcom integrations.
EasyEcom
Get EasyEcom integrated into your app
Our team understands what it takes to make a EasyEcom integration successful. A short, crisp 30 minute call with folks who understand the problem.