Sync Draft Orders Between Nue and Salesforce

overview the sync draft orders feature enables seamless, bidirectional synchronization of draft (unactivated) orders—including all line items, discounts, and billing settings—between nue and salesforce draft orders can be initiated from either direct sales (salesforce) or self service (nue) this feature supports critical use cases such as tracking self service cart abandonments for sales follow up pushing direct sales draft orders to the billing portal for customer self checkout ensuring that any changes made to draft orders propagate accurately before activation why it matters increases revenue capture by enabling reps to monitor and follow up on abandoned self service carts, reducing missed opportunities streamlines deal closure by allowing reps to initiate draft orders in salesforce and push them to the billing portal for customer self checkout, reducing sales cycle friction ensures billing accuracy by propagating all relevant fields (billing, discounts, custom fields) and preventing duplicate or out of sync orders across systems setup & configuration enable draft order sync in nue to enable draft order synchronization, administrators need to configure the sync settings in the nue platform navigate to settings in your nue admin panel locate the salesforce integration section enable the sync draft orders setting once enabled, the system will automatically sync draft orders created in nue to salesforce (if auto sync is enabled) listen for webhooks to process draft order events salesforce configuration in salesforce, users will see a sync order button on draft order records that allows manual synchronization to nue sync workflows nue → salesforce (automatic) when a draft order is created in nue through the self service portal the order is created with status draft in nue if auto sync is enabled, a webhook event ( order created ) is triggered the system checks if the sync draft orders setting is enabled the order, along with customers, order products, line items, and pricing dimensions, is synced to salesforce external ids are mapped bidirectionally to maintain referential integrity salesforce → nue (manual) sales representatives can push draft orders from salesforce to nue rep creates or modifies a draft order in salesforce rep clicks the sync order button nue creates or updates the draft order with all associated data the customer can then complete self checkout in the billing portal use cases & examples use case 1 cart abandonment recovery a saas customer's end user begins a self service checkout in the billing portal but abandons the cart before completing payment draft order automatically syncs to salesforce sales rep receives notification of abandonment rep reviews the customer's cart details rep initiates a follow up call rep can complete the order directly from salesforce or guide the customer to complete self checkout use case 2 sales assisted checkout a sales rep working on a complex enterprise deal rep prepares a quote and draft order in salesforce rep finalizes it into a draft order using the sync order button, rep pushes to nue customer receives a link to the billing portal customer completes self checkout and payment system updates status in both salesforce and nue technical implementation webhook events the system uses webhooks for real time synchronization order created triggered when a draft order is created source of truth rules to maintain data integrity activation respects origin orders can be activated from either system, but the activation always respects the system of origin if a nue origin order is activated in salesforce, it triggers activation in nue and syncs back to salesforce if a salesforce origin order is activated in nue (customer self checkout), it triggers activation in salesforce and syncs back to nue this ensures the originating system's data and business rules are always respected field precedence during sync, the sending system's data takes precedence limitations & considerations current limitations no deletion sync order deletion is not synchronized between systems orders must be manually deleted in each system if needed best practices always verify critical order details after sync use the sync feature before order activation to ensure data consistency monitor webhook logs for any failed sync attempts ensure customer and contact records exist in both systems before syncing orders