DBD: Integration with DB Commerce

Buyer Setup 

You will need to set up a buyer for each customer site on DB Commerce.  This is done through the eCommerce Toolkit menu screens on DB Distributor.  

Navigation: DB Distributor Toolkits > eCommerce > Setup > Buyers 

The required fields are located on tabs 1 - Setup and 4 - Catalog.   

Setup Tab 

• Buyer’s ID code: Must be exactly 10 characters. The first 2 characters are the division code, and the following 8 are the customer code (padded with zeros or spaces as needed).
• Buyer’s password: Set this to match the exact 10 characters used for the Buyer’s ID Code.
• Buyer’s Customer Code: This is the customer code where the orders will be created. Make sure to change this if you are copying details from an existing buyer record.

Catalog Tab 

• EC Catalog ID: A catalog is required for the integration to function. We recommend creating a dummy catalog with no items that isn't tied to a real live customer - something like 00000000   works perfectly.

Automated Buyer Setup 

If you want to speed up this process, you can use a built-in utility to automate creating the EC Buyer record and adding the customer to the Data Rep Filter at the same time. This utility automatically populates all required fields using the correct formatting.

Navigation: DB Distributor > Accounts Receivable > Setup > DBE Customer Setup in DBD 

If you set this up as a parameter record, you only need to fill in two fields:

1. Catalog ID: This acts as the default catalog when building the DB/d buyer record.
2. Target Code: Set this to your replicated data set for DB Commerce (usually DB_ENTERPRISE  ). This tells the system to automatically add the customer code into your replication filter.

💡 Shortcut: You can also access this directly from your main customer setup screen by clicking “Setup DBE Records”. Doing it this way locks the fields so you can simply click Proceed to build the record and add the customer to the filter immediately. You will also be asked if you want to kick off a replication right then and there.

eCommerce Customer Parameters  

Set this up if you want the system to look for custom EC Item Parameters for each item and to establish a default warehouse for the customer.

Navigation: DB Distributor Toolkits > eCommerce > Setup > Customer Parameters 

• If you want a default warehouse applied to their web orders, set it on Tab 4.
• If you don't need a default warehouse, you just need to create the record, save, and exit. 

eCommerce Item Parameters  

Once your Customer Parameters are live, you can specify whether a DBc order should automatically generate a vendor Purchase Order inside DBd.

To set this up, open your Custom Item Setup/Inquiry screen for an item. When you exit, the system will open an additional window called eCommerce Item Parameters.

• On Tab 3 (Ordering), check the box for Create P/O on order.
• If you leave this box unchecked, the system assumes the incoming order from DBc is a standard release of your existing inventory rather than a fresh purchase order.

Data Replication Filter  

Within DBd, you can choose exactly which customers sync to the web. This keeps your data clean by only replicating accounts that actually use DB Commerce, preventing non-web customer data from clogging your sync queue.

Navigation: DB Distributor Optional Modules > Data Replication > Setup > Apply Filters 

1. In the Target Code field, select your DBc data replication target (usually DB_ENTERPRISE  ).
2. In the Select Filter field, choose the specific customer(s) you want to sync, then click Apply Filter.

🔄 Need to force a sync? If you ever feel like your DBd and DBc data are drifting out of sync, check the box next to a customer and click the Replicate button to push all of their data fresh. Just be sure to check your data rep queue first to make sure you aren't already sitting in a processing backlog.

⚠️ Pro-Tip for Large Replications: If you need to re-replicate a massive volume of customer records, start the process at the end of the day on Friday. This allows the heavy data processing to run over the weekend without dragging down daily operational speeds for your team. If you constantly find yourself running large volumes of data, give us a shout at support@demandbridge.com so we can help you set up multiple data streams to boost your sync speeds!

Unattended Printing 

The printing of Purchase Orders and Packing Lists within DBd typically happens automatically via a background process known as Unattended Printing.

By default, Unattended Printing is configured to look for standard numeric order ranges (like 00-000000   to 99-999999  ). Because web orders coming out of DB Commerce use alphanumeric characters in their numbering sequences, your standard printing rules won't automatically catch them.

To fix this, you will need to tweak your existing settings or add a distinct range to handle DBc orders separately. If you need a hand setting up these printing ranges, open a ticket with a DemandBridge support representative and we'll get you squared away!