CalvinBackup/erpnext
1
0
Fork 0
mirror of https://github.com/frappe/erpnext.git synced 2026-02-12 17:23:38 +00:00
Code Issues Packages Projects Releases Wiki Activity

Created Designing Integrations (markdown)

Rushabh Mehta
2018-06-25 12:07:27 +05:30
parent 1c012b9e96
commit 7115aef879
1 changed files with 9 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files

9
Designing-Integrations.md Normal file

@@ -0,0 +1,9 @@
### Avoid 2-way sync
Two way syncing is not a good idea unless its absolutely necessary. If you are integrating with a 3rd party marketplace or e-commerce, try pulling in orders and customers and pushing fulfillment. If you try 2-way sync for items, it will not scale well and also conflicts get hard to manage.
### Use Generic Names in Standard Workflow
In the standard workflow, use generic names first and then add custom fields to specify which is the exact provider.
For example if you are integrating with Fedex, in the Delivery Note, add "Shipping Provider" as the link and within Shipping Provider, add custom fields for Fedex (if needed). So all integration code is maintained separately and does not seep into the core workflow.