PROPOSAL SUMMARY
This proposal covers the scope of BigCommerce – NetSuite Integration via REST API.
REQUIREMENT
A solution to sync the Items, customers, Orders, Shipments, Refund between Big Commerce and NetSuite.
PREREQUSITES
- Need to create Account API prior to integration in Big Commerce. Only store owner account in Big Commerce can set up Account API. So, the store Owner credentials should be provided prior to integration development.
- Share the COA account needs to be used for PayPal and credit card payment in NetSuite
DELIVERABLES
We will be managing following syncs between Big commerce – NetSuite via REST APIs.
- Item Sync (NetSuite – Big Commerce):
– In item sync, updation base price of item from NetSuite to website is only considered. This will be a real time sync. Item Name in NetSuite (SKU in website) will be used as item reference.
– We assume that items in NetSuite are already synced to NetSuite.
- Customer Sync (Big Commerce – NetSuite):
1) Existing customer sync: Existing customers in Big commerce will be synced from Big commerce to NetSuite
2) New customer sync: when new customer places an order in Big Commerce, customer will be created at the time of order creation in NetSuite
- Order Sync, Item Fulfillment sync (NetSuite – Big Commerce):
– When an order is changed to status ‘completed’/’shipped’ in Big Commerce
– For ‘shipped’ orders Item Fulfilment and Cash sale will be created in NetSuite
– For ‘completed’ orders, Cash sale will be created in NetSuite.
– Cash sales will be posted to the accounts according to the payment method (credit card / paypal)
The above actions will be performed on scheduled basis, not in real time.
- Refund Sync (NetSuite – Big Commerce):
When a cash refund on credit memo is created in NetSuite for the Sales order in NetSuite, the sync will pass refund information such as refund amount and quantity refunded to BigCommerce along with updating the order status as Refunded.
ASSUMPTIONS
- The scope only includes the Existing customer sync, order sync, shipment sync, refund sync, item sync. The changes outside of the proposal will be considered as additional change request.
- The field mappings will be provided prior to development.
- We assume that items are created in Big Commerce with the ‘Item Name’ as ‘SKU’
RISKS
- The proposal is prepared based on Big Commerce standard API documentation. We have not tested the APIs since Account API is not set up. And we assume that the API will work and return response as per the documentation. In case of API failures, we may need to investigate further for other solutions.
- If items in the sales order is not available in NetSuite, sales order creation will fail.