Skip to main content
FieldKo stores all its data in Salesforce objects, so you integrate it the same way you integrate any Salesforce data: with Salesforce APIs or a middleware tool that uses them. Use this page to plan the common retail execution integrations, set up a safe integration user, and avoid side effects on reps and FieldKo’s own automation.

​
User Permissions Needed

​
Common Integration Patterns

Most retail execution integrations follow these patterns. Use the object labels in this table to find each object in Setup > Object Manager and in your middleware. For the full list of objects and how they relate, see FieldKo Data Model and Export FieldKo Data and Photos.
FieldKo uses its own product, price book, and order objects, not the standard Salesforce Product, Price Book, and Order objects. A connector that writes to the standard objects doesn’t change what reps see in the app. Map your integration to the FieldKo objects.

​
Orders to Your ERP

To send orders to your ERP, have your middleware pick up new FieldKo orders and their line items, and then record the result on the order:
  • Add your own fields for the handoff, such as ERP Order Number and ERP Status, instead of changing Status. Reps choose Status at checkout, and the app never offers Sent or Send Failed, which FieldKo reserves.
  • Orders arrive when reps sync, so line items can arrive in a later batch than their order. Process an order only when its line count is complete: the Is Total Order Line Items synced? field is true when the order’s line count matches its lines.

​
Master Data from Your ERP

Load master data in dependency order: accounts, then products, then price books and entries, then contracts and ranging. See Import and Update Data. Remember that FieldKo applies its own rules, for example:
  • When a FieldKo product becomes Inactive, FieldKo deactivates its price book entries and product set lines.
  • When an account’s owner changes, FieldKo can move future visits and share recent orders with the new owner, depending on Transfer Data On Change Of Account Owner. See Remove a Rep’s Access.
  • Reps get only the price books linked to their accounts through an active FieldKo contract, and that are active and valid today. See Set Up Products, Ordering, and Ranging.

​
Use External IDs and Upsert

The FieldKo packages don’t include external ID fields on accounts, products, or price books. Create your own, so your integration can upsert records by the ERP’s key instead of storing Salesforce record IDs:
  1. On each object you load, create a text field, such as ERP Product Code, and select External ID and Unique.
  2. Upsert records on that field. Reference parent records by their external IDs too, for example a FieldKo Pricebook Entry’s FieldKo Product by ERP Product Code.
Every custom field on Account syncs to the app. Keep integration-only account fields few and short. See Which Fields Sync.

​
Set Up an Integration User

Run each integration as its own user, never as a rep or admin:
  1. Create a user with the Salesforce Integration user license, if your contract includes it, and an API-only profile. For license options, see User Licenses in Salesforce Help, or ask your Salesforce account executive.
  2. Create a permission set that grants only the object and field access the integration needs, such as read on FieldKo orders and edit on FieldKo products. Assign it to the integration user.
  3. If your org assigns licenses for the FieldKo packages, assign the integration user a license for each package whose objects it uses.
  4. Assign your automation bypass permission set. See Avoid Triggering Rep-Facing Automation.
The integration user doesn’t need a FieldKo permission set, because it doesn’t use the FieldKo Atlas app. For access design, see Profiles, Permission Sets, and Permission Set Groups.

​
Choose an API or Tool

Which objects you can use with Change Data Capture, and how many events you can deliver, depends on your edition and add-ons. Check your Salesforce contract or ask your Salesforce account executive. Every API call counts toward your org’s API allocation, which the FieldKo Atlas app also uses when reps sync. See API and Platform Limits.

​
Avoid Triggering Rep-Facing Automation

Large loads can fire your own flows thousands of times, such as manager alerts on every order. Give integration users a custom permission, and check it in your flows. See Bypass Your Flows for Integration Users. FieldKo’s own triggers and flows always run, for integration users too. Records you load must follow FieldKo’s rules: for example, every visit needs an account, a sales representative, and a date inside an active call cycle for that rep. If a bulk load fails with time or CPU limit errors, reduce the batch size in your tool.

​
See Also

Last modified on October 20, 2026