Snapify Snapify Snapify Snapify Snapify Snapify Snapify Snapify Snapify Snapify Snapify Snapify Snapify Snapify Snapify Snapify Snapify Snapify Snapify Snapify Snapify Snapify Snapify Snapify Snapify Snapify Snapify Snapify Snapify Snapify Snapify Snapify Snapify Snapify Snapify Snapify Snapify Snapify Snapify Snapify Snapify Snapify Snapify Snapify Snapify Snapify Snapify Snapify Snapify Snapify Snapify Snapify Snapify Snapify Snapify Snapify Snapify Snapify Snapify Snapify Snapify Snapify Snapify Snapify Snapify Snapify Snapify Snapify Snapify Snapify Snapify Snapify Snapify Snapify Snapify Snapify Snapify Snapify Snapify Snapify Snapify Snapify Snapify Snapify Snapify Snapify Snapify Snapify Snapify Snapify Snapify Snapify Snapify Snapify Snapify Snapify Snapify Snapify Snapify Snapify Snapify Snapify Snapify Snapify Snapify Snapify Snapify Snapify Snapify Snapify Snapify Snapify Snapify Snapify Snapify Snapify Snapify Snapify Snapify Snapify Snapify Snapify Snapify Snapify Snapify Snapify Snapify Snapify Snapify Snapify Snapify Snapify Snapify Snapify Snapify Snapify Snapify Snapify Snapify Snapify Snapify Snapify Snapify Snapify Snapify Snapify Snapify Snapify Snapify Snapify Snapify Snapify Snapify Snapify Snapify Snapify Snapify Snapify Snapify Snapify Snapify Snapify Snapify Snapify Snapify Snapify Snapify Snapify Snapify Snapify Snapify Snapify Snapify Snapify Snapify Snapify Snapify Snapify Snapify Snapify Snapify Snapify Snapify Snapify Snapify Snapify Snapify Snapify Snapify Snapify Snapify Snapify Snapify Snapify Snapify Snapify Snapify Snapify Snapify Snapify

Connect with ease

Distributors/Retailers place ~18 million POs with Manufacturers/Wholesalers everyday in the US and it should not be this hard

Connect with ease

Distributors/Retailers place ~18 million POs with Manufacturers/Wholesalers everyday in the US and it should not be this hard

What'S the probleM Today?

First, defining terms

Merchant = distributor/retailer
Vendor = manufacturer/wholesaler

Now, the data

In the US there are approx. 600,000 b2b distributors and 1,200,000 b2c retailers
These 1.8 million Merchants send an avg of 10 POs to Vendors everyday
So Merchants place ~18 million POs per day with Vendors in the US
Meaning 4.5 billion POs per year
That's just POs from Merchants to Vendors

But a Merchant sending a PO to a Vendor electronically is fraught with peril

Merchant Sends a PO via Email

This requires manual order entry by the Vendor, unless the Vendor uses expensive and old OCR tech to automate receipt of the PO

Merchant enters a PO in vendor portal

This requires manual order entry by the Merchant

Merchant sends a PO via edi

EDI is asynchronous when transacting flat files, so discrepancies lie dormant waiting for a human to realize there's a problem, intervene and solve the issue

Extraordinary EDI testing is undertaken to address this asynchronous architecture and eliminate all discrepancies that will become latent issues in your fulfillment chain

This also adds a third set of system requirements to the tech stack, namely those of the EDI provider

Merchant sends a po via punchout

This requires a web store intermediary, yes the Vendor can maintain the product data in the web store, but this is basically a glorified Vendor portal and yet again adds a third system

What would be easier?

Directly connecting Merchants and Vendors via API

OPTION 1: Map API endpoints

a. Merchant identifies all the PO fields in the Merchant ERP, per ANSI ASC X12 standards

b. Merchant requests and Vendor provides the corresponding API endpoints in the Vendor ERP

c. Merchant ERP is configured to send POs directly to the Vendor ERP via API using JSON data over HTTPS

d. Upon receipt of a Merchant PO the Vendor ERP tests and validates the following:

Header data - Customer name, Acct #, Order type (standard, rush, blanket)
Financial data - Payment terms, Tax exemption, Min PO value
Shipping data - Address fields, Carrier acct
Item data by order line - MPN, Cost, Min qty, Inc qty, UOM
Data format - All fields conform to vendor requirement

e. If the Vendor ERP identifies any discrepancies it rejects the PO and synchronously (instantly) returns a reject/error message to the Merchant ERP = PO canceled, Fix ___ fields and Resubmit a new PO

Or, if possible, Vendor ERP could offer instant solution options for errors, like how UPS offers instant address fixes in ecommerce checkouts

f. If the Vendor ERP identifies no discrepancies then it accepts the PO and synchronously (instantly) returns an accept/success message to the Merchant ERP = PO accepted, Thank you

OPTION 2: MERCHANT Builds a native App

a. Merchant builds an approved app for the Vendor ERP system(s) and lists the app in the Vendor ERP App Store(s)

b. The app includes a preset list of the PO fields in the Merchant ERP, per ANSI ASC X12 standards

c. Vendor installs the app in the Vendor ERP and maps the Merchant PO fields

d. This sets the API endpoints so the Merchant ERP can send POs directly to the Vendor ERP via API using JSON data over HTTPS

e. Everything works the same as Option 1 from step "c" down

OPTION 3: VENDOR Builds a native App

a. Vendor builds an approved app for the Merchant ERP system(s) and lists the app in the Merchant ERP App Store(s)

b. The app includes a preset list of the PO fields in the Merchant ERP, per ANSI ASC X12 standards

c. Merchant installs the app in the Merchant ERP and maps the Vendor PO fields

d. This sets the API endpoints so the Merchant ERP can send POs directly to the Vendor ERP via API using JSON data over HTTPS

e. Everything works the same as Option 1 from step "c" down

Examples of ERP App Stores

SAP Store

Netsuite SuiteApp

MS Dynamics Appsource

Infor Marketplace

Acumatica Marketplace

Syspro App Store

Odoo Apps

Connect with ease

Connect with ease

Please GIVE US feedback!

Read on for the whole story...

What'S the probleM Today?

Merchant Sends a PO via Email

Merchant enters a PO in vendor portal

Merchant sends a PO via edi

Merchant sends a po via punchout

What would be easier?

OPTION 1: Map API endpoints

OPTION 2: MERCHANT Builds a native App

OPTION 3: VENDOR Builds a native App

Examples of ERP App Stores

Contact Us

Ask A question

Connect with ease

Connect with ease

Please GIVE US feedback!

Read on for the whole story...

What'S the probleM Today?

Merchant Sends a PO via Email

Merchant enters a PO in vendor portal

Merchant sends a PO via edi

Merchant sends a po via punchout

What would be easier?

OPTION 1: Map API endpoints

OPTION 2: MERCHANT Builds a native App

OPTION 3: VENDOR Builds a native App

Examples of ERP App Stores

Contact Us

Ask A question

This website uses cookies.