Skip to main content

Business Central

Sync warehouse inventory by location​

When you'd use this: When you need to sync warehouse stock levels from Business Central to your store, CommerceBuild automatically pulls inventory data separately for each active warehouse location to ensure accurate, location-specific stock information.

What happens automatically:

When syncing warehouse details from Business Central, the platform queries each active warehouse location individually. This ensures:

  • Inventory data is retrieved for all warehouses marked as active in your store
  • Each warehouse's stock levels are synced independently
  • The sync process handles location-specific filtering correctly
  • Only warehouses that are active (warehouses with the inactive flag set are excluded) are included

The platform connects to the Business Central stock inventory endpoint to retrieve the latest warehouse data for your store.

Troubleshooting:

  • Warehouse inventory not appearing in Store Manager — The sync process filters warehouse data by location code. Verify that the warehouse is marked as active in your store's warehouse configuration (not flagged as inactive in warehouse extras). Inactive warehouses are automatically excluded from the sync.
  • Warehouse details sync failing — If warehouse inventory stops syncing, verify that the Business Central stock inventory endpoint is responding correctly. Check the integration logs for connection errors or timeouts between CommerceBuild and Business Central.

Attach remittance documents to orders in Business Central​

When you'd use this: When customers pay by bank transfer and upload a remittance document (such as a PDF or image) during checkout, that document is automatically attached directly to the sales order in Business Central so your fulfilment team can verify payment.

What happens automatically:

When a customer completes checkout with bank transfer payment and uploads a remittance document:

  • The document is sent to Business Central through the CommerceBuild connector
  • The file is attached directly to the sales order as a document attachment
  • The attachment appears on the sales order record in Business Central, not as a separate incoming document
  • Your fulfilment team can view the remittance proof alongside the order details

Troubleshooting:

  • Remittance document not appearing on the sales order — Check that the order was successfully created in Business Central and that the document was uploaded before the customer completed checkout. The attachment is created at the same time as the order.

Create sales quotes from checkout​

When you'd use this: When you want customers to request a quote through your storefront checkout, CommerceBuild sends the quote details to Business Central where it's created as a sales quote record for your sales team to review and convert to an order.

What happens automatically:

When a customer submits a quote request through checkout:

  • The quote details are sent to Business Central through the CommerceBuild connector
  • A sales quote record is created in Business Central with the customer details, line items, quantities, and pricing
  • The quote appears in Business Central where your sales team can review, modify, and convert it to a sales order
  • CommerceBuild automatically filters out checkout-specific data that Business Central doesn't expect (such as internal checkout identifiers and purchase order mapping fields), sending only the information needed to create a valid sales quote

Troubleshooting:

  • Quote not appearing in Business Central — Verify that the quote was successfully submitted through checkout and that the customer account exists in Business Central. Check the integration logs for any connection or data errors between CommerceBuild and Business Central.

Sync unavailable periods from Business Central​

When you'd use this: When you manage block dates or unavailable periods in Business Central (such as warehouse closures, maintenance windows, or shipping blackout dates), CommerceBuild syncs these periods to your store so customers can't place orders for affected dates.

What happens automatically:

When syncing unavailable periods from Business Central:

  • The platform retrieves all unavailable period records, including their start dates, end dates, and status
  • The sync maps the Business Central entry status to the active status in CommerceBuild, ensuring deleted entries in Business Central are properly reflected as inactive in your store
  • Only active unavailable periods appear as restrictions in your storefront
  • Changes to unavailable periods in Business Central are reflected in your store after the next sync

Troubleshooting:

  • Unavailable period not appearing in store — Verify that the period is not marked as deleted in Business Central. Deleted entries are synced as inactive and won't block order placement. Check that the entry's dates are correctly configured in Business Central.
  • Deleted period still blocking orders — If an unavailable period was deleted in Business Central but still appears active in CommerceBuild, trigger a manual sync to update the entry status.

Display customer-specific item codes and descriptions​

When you'd use this: When your customers use their own item codes and descriptions that differ from your internal Business Central item numbers, CommerceBuild syncs these customer-specific references so customers see familiar product identifiers when browsing and ordering.

What happens automatically:

When syncing item references from Business Central:

  • The platform retrieves all Item Reference records where the reference type is set to Customer
  • For each customer-item combination, CommerceBuild syncs the customer's item code, description, and unit of measure
  • When a customer logs in to your store, they see their own item codes and descriptions instead of your internal product names
  • Changes to item references in Business Central are reflected in your store after the next sync

For example, if your Business Central item 1900-S is named "Paris Guest Chair, black" but your customer refers to it as "Z1900" with the description "Paris Lounge Chair", the customer will see their own code and description when browsing your store.

Troubleshooting:

  • Customer not seeing their item codes — Verify that the Item Reference record in Business Central has the reference type set to Customer and that the customer code matches the logged-in customer. Only customer-type references are synced to CommerceBuild.
  • Item description not updating — If you've changed an item reference description in Business Central but the customer still sees the old description, trigger a manual sync to update the customer product data.

Restrict invoices by ship-to address​

When you'd use this: When you have B2B customers with multiple ship-to addresses and you want to restrict what each user can see based on their shipping locations, CommerceBuild uses the ship-to code from invoices to filter the transaction list so users only see invoices for locations they have access to.

What happens automatically:

When ship-to user restriction is enabled:

  • CommerceBuild syncs the ship-to code from each invoice in Business Central
  • For invoices posted from a sales order, the ship-to code is resolved from the order details
  • For invoices posted without a sales order (such as drop-ship or vendor-billed transactions), the ship-to code is read directly from the posted invoice header in Business Central
  • Users with ship-to restrictions only see invoices that match their permitted locations
  • Invoices without a resolved ship-to code are not visible to restricted users

What you need first:

To sync ship-to codes from invoices posted without sales orders, your Business Central custom field setup must include the Ship-to Code field (table 112, field 12) in the posted sales invoice header custom fields. This allows CommerceBuild to retrieve the ship-to code that Business Central stores on the invoice itself.

Troubleshooting:

  • Invoices disappearing when ship-to restriction is enabled — If invoices were posted in Business Central without a sales order and the ship-to code is not included in your posted invoice header custom fields, those invoices cannot be attributed to any ship-to location and will be hidden from all restricted users. Add the Ship-to Code field (table 112, field 12) to your Business Central custom field setup for posted sales invoice headers, then trigger a manual sync to resolve the ship-to codes.
  • Drop-ship invoices not appearing for restricted users — Verify that your Business Central custom field configuration includes the Ship-to Code field from the Sales Invoice Header table. Without this field in the custom field setup, CommerceBuild cannot retrieve the ship-to code from invoices that were posted directly without going through a sales order.

Sync orders and invoices separately for each customer​

When you'd use this: When customers view their transaction history in the storefront, CommerceBuild tracks orders and invoices as separate sync operations to ensure that a long-running invoice sync doesn't prevent orders from loading, and vice versa.

What happens automatically:

When a customer accesses their transaction history:

  • The platform tracks the last successful sync time separately for orders and for invoices
  • If an order sync is in progress, customers can still trigger an invoice sync without waiting
  • If an invoice sync is in progress, customers can still trigger an order sync without waiting
  • Each sync type checks only its own last sync time to determine whether a new sync is needed

Troubleshooting:

  • Transaction sync reports failed when only one transaction type is affected — If you see a sync failure for orders or invoices, verify which sync type failed by checking the sync status for each separately. A failure in one sync type doesn't prevent the other from completing successfully. Retry the failed sync type without affecting the other transaction data.

Troubleshoot failed payment posts in Payment Management​

Where to find it: Admin → Payment Management → Failed Invoices (/admin/morders/failed_invoices)

When you'd use this: When a payment capture succeeds but CommerceBuild can't post the payment to Business Central, the failure appears in Payment Management with the specific Business Central error message so you can diagnose and resolve the issue.

What happens automatically:

When a payment post to Business Central fails:

  • The payment capture is recorded as retryable rather than success, preventing funds from being captured without a corresponding Business Central record
  • The actual Business Central error message appears in Payment Management, including details like correlation IDs for deadlock errors, configuration issues, or connection timeouts
  • The error message shows you whether the failure can be safely retried (such as a temporary database lock) or requires configuration changes (such as an incorrect bank account mapping)

Troubleshooting:

  • Payment marked retryable instead of success — This is correct behaviour when Business Central doesn't confirm the post. The failure detection prevents recording a payment as posted when funds were captured but no Business Central record was created. Review the specific error message to determine whether to retry or fix a configuration issue.
  • Error message missing or not helpful — If you see a generic error message instead of the specific Business Central response, check the integration logs for the full error details. The actual Business Central error, including correlation IDs and table names, should appear both in Payment Management and in the gateway exchange logs.