Logicbroker Direct is an offering that allows suppliers to automate and configure their integration using advanced Logicbroker features and configurations. Suppliers can shift their focus from operations to growing their footprint within their market.
Why Logicbroker Direct?
Logicbroker Direct is designed for growing small-medium-sized suppliers who want to take control of their e-Commerce integrations and expand their partnership network. New and existing suppliers can select preferred integration methods (manual/web-based, EDI or API) and add higher-level functionality.
Getting Started
To get started with Logicbroker Direct:
- Review the Logicbroker Direct features and make sure they fit your company’s needs
- Reach out to platformsales@logicbroker.com to request a demo, discuss the offering, review partners and sign the contract
- Our Client Experience Onboarding Team will reach out with a Logicbroker Direct Survey where you are able to select your features and configure your integration
- Complete the survey and work on implementation and onboarding with our Client Experience Team
Features: Logicbroker Direct vs. Portal
The table below provides a comparison of the features when integrating with the Portal and with Logicbroker Direct.
| Feature | Description | Portal | Logicbroker Direct |
|---|---|---|---|
|
Workflows |
Logicbroker is able to configure the way a company will receive different documents which provides flexibility with document statuses. |
Standard |
Configurable |
|
Document Automation |
Allows for automatic acknowledgment and invoice creation using PO and ASN information. |
N/A |
Available |
|
Business Rules |
Allows suppliers to map to retailer’s specifications easier. |
Standard |
Up to 5 Configurable |
|
Portal Configurations |
Allow suppliers to run automated rules to avoid validation compliance errors and automate document statuses. | N/A |
Configurable |
|
Packing Slips |
These are Logicbroker-mapped documents that comply with partner specifications. |
Standard |
Configurable (Partner approval is required) |
| Reporting | This is used for monitoring documents and providing a drill-down view of all documents and counts |
Standard |
Configurable |
|
Support |
Run by our Client Experience Team, this team oversees onboarding and day-to-day production issues. |
Production Team |
Dedicated onboarding support throughout onboarding/implementation then handed off to the Production Team |
Features and Their Use Cases
Update Order Items with Data from Inventory Feed
Export Packing Slip to FTP
Logicbroker-generated packing slips are sent to suppliers through the FTP.
Use case: EDI suppliers who would like to use Logicbroker-generated packing slips and not have to log into the portal to access them. This would eliminate the need for EDI suppliers to map their own slips.
All packing slips will be sent to the same folder, we do not support retailer-specific folders.
Update Order Items with Data from Inventory Feed
Orders sent from retailers are updated in Logicbroker to reflect information suppliers upload on their inventory feed including cost, description, color, etc.
Use case: Some retailers may send orders without certain information which may be valuable to the supplier to process orders efficiently.
The information must be present and accurate in the inventory feed for the workflow to run correctly.
Update Document Status
Documents are updated, and statuses change based on workflows that work best for the supplier.
Use case: Some retailers do not accept certain documents, but suppliers may need to have a record of them (such as invoices). Suppliers can set up workflows to automatically move documents to ‘Complete’ in Logicbroker to use for reporting/accounting purposes later.
Cancel Old Orders
Orders are automatically canceled if they reach a specific age in hours.
Use case: Lingering orders may cause inaccurate data and missing information in the retailer’s system. This workflow will generate a cancellation to be sent to the trading partner.
Change Schedules
Documents and workflows run either automatically or on schedules. This feature allows suppliers to control what time those schedules run and how often.
Note: Schedules that are on the retailer side cannot be changed as they will affect other suppliers.
Auto-acknowledgment
Any order that reaches Logicbroker will automatically trigger an acceptance acknowledgment to be created and sent out to the retailer. Partner-specific configuration is supported.
Some retailers do not accept auto acknowledgments in which case this can be turned off for that specific partner. If orders need to be canceled, the supplier can do so and the new cancel ack will be sent out.
Use case: Some retailers require acceptance acks for all orders. This feature allows for automation in creating this document. Any shipment created in or sent to Logicbroker will trigger an invoice document to be created and sent out to the retailer. Partner-specific configuration is supported.
Auto-invoice
Any shipment created in or sent to Logicbroker will trigger an invoice document to be created and sent out to the retailer. Partner-specific configuration is supported.
Use case: Some retailers require invoice documents for all shipped orders. This feature allows for automation in creating and sending this document. Some retailers do not accept invoices and require suppliers to invoice outside of Logicbroker. This configuration does not support those instances. Auto-invoicing generates a random invoice number. If the supplier needs a specific invoice number to be sent, this configuration will not work.
Copy Ship Method from Order to Shipment
Ignore Documents Linked to Ignored Orders
Copy Ship Method from Order to Shipment
Ship methods on shipments will be defaulted to what the retailer sent on the order.
Use case: Retailers may not accept certain ship methods or variations of the code that is sent. Suppliers can ship with the correct ship method and not have to worry about the code not matching up to exactly what the retailer is looking for.
Suppliers are still expected to ship using the appropriate method.
Ignore Documents Linked to Ignored Orders
Any documents coming into Logicbroker or created in Logicbroker will be moved to Ignored if the order is in an Ignored status.
Use case: Some orders may be ignored because they are duplicates, incorrect, or are no longer of use. This configuration allows for a more accurate report of relating documents.
Ignore Unlinked Documents
Documents that are sent into Logicbroker that are not tied to any order will be automatically ignored.
Use case: Some suppliers may try to send return documents (acks, shipments, invoices, returns) for orders that were transmitted before their integration with Logicbroker. These documents cannot be sent over to the retailer as the PO does not exist in our system.
Any order that was sent to the supplier before integrating with Logicbroker needs to be handled outside of Logicbroker.
Logicbroker can add up to 5 rules that allow suppliers to do numerous things including:
- Default Required Information on Documents
- Map Certain Fields to Specified Partners
- Generate Container Codes
Business rules are often used to facilitate the mapping and validation of documents between partners. These are put in place for various reasons- to default required information, to map certain fields to certain partners, to generate container codes, etc.
If an integration runs into any issues, a business rule may help. These are often individual use cases.
With this offering, users are permitted up to 5 business rules. Additional rules may come at an additional charge.
Use Cases:
- You are a supplier, and you send a fulfillment code on each line item. Since you are connected to different retail channels, each retailer requires a different fulfillment code than the standard you send Logicbroker. Logicbroker can then employ a business rule for each of your retail channels that correctly maps to the retailer’s specification.
- Logicbroker will make sure that your tracking numbers and container codes meet GS1 requirements if you are trading with a retailer that requires specific container codes per box. This is useful when your system is unable to provide detailed container information. Logicbroker can then use business rules to insert this data, where required based on your retailer’s specifications.
Logicbroker can request to have packing slips generated in the portal altered if suppliers obtain retailer approval. Changes we can make include:
- Adding Supplier SKU
- Add description
- Map carrier codes
Suppliers have the option to use Logicbroker-generated packing slips; or for EDI/API suppliers, they can choose to map their own and have them approved by the retailer prior to going live. For suppliers wanting to use Logicbroker packing slips, they can ask our team to make changes that would facilitate operations on their end.
Suppliers would have to obtain retailer approval for any changes and provide this proof to Logicbroker before we can implement the changes.
Use case:
You would like your company’s SKU to appear on the slip to make it easier for your warehouse team to pull orders.
Logicbroker can add specific document fields onto our reporting tool using a customized report that will allow suppliers to track document information.
The Advanced Export section of the Portal can be used to download system data in a variety of formats, including CSV, XLSX, XML, and JSON. It can also be used to create template profiles that can be used to download specific data for reports, imports, and other activities. With Logicbroker Direct, suppliers are able to request special fields to be populated onto a report.
This would require development work, fields and filtering are self-serviceable, but additional fields outside of this scope can be added by Logicbroker.
Use case:
A retailer uses a special ID number to reference a document. It is not present as a field in the Advanced Export tool but is present on the order. Suppliers can ask for this specific value to be populated in a report.
Logicbroker’s Onboarding Team will walk suppliers through onboarding and implementing any feature changes. Once complete, they will work with the Production Team for day-to-day issues.
Please discuss with sales for any features outside of this list to make sure they can be supported.
- Onboarding takes care of integrating suppliers with partners and assisting with any implementation requests.
- Our production team helps with day-to-day production issues and requests made after a supplier is already live with a partner.
Comments
Please sign in to leave a comment.