B2C to B2B Crunch Time – A Strong Case for Accounting Integration

April 14th, 2014

Sales Order ClutterTell us if this sounds like your business… so you started selling on eBay, then you added an Amazon store, but by then you had a ton of orders and along with that came the headaches and eventually a full-on migraine. It was then that you decided to take all that pain away with an eCommerce store, and everything leveled out. Then, another large batch of orders rolled in and along came some buyers from companies that wanted to re-sell your items in their stores. Each of those buyers placed huge orders, which you had to discount in your accounting system, which led to even more work. This is what we call “B2C to B2B Crunch Time” and we’re going to explain to you how to avoid it.

You first need to choose an eCommerce cart which will allow you to create a login for B2B customers, which will offer them their own pricing tiers and products. You will also be able (depending on your cart selection) to create skins for your B2B customers which can provide branding allowing you to cater to your each B2B customer individually. This simple change also allows you to maintain your B2C presence without the two worlds colliding.

So now that you have solved that problem it’s on to the same old problem… all those orders.

How can you possibly key in your B2B and B2C orders and do inventory all at the same time?

When B2C to B2B Crunch Time occurs you really need to consider an integration solution, which will allow you to pull down all those orders into your accounting system and take away the tedious manual entry of those orders. The integration solutions offered by eBridge Connections will not only pull in those orders in automatically into your accounting system, it will also send updated tracking information, inventory and products all back up to your store. In addition, new customer entries can be added automatically if they don’t currently exist in your accounting system.

Does this sound like something you might need? Of course it is.

Let eBridge Connections help you get past the B2B to B2B Crunch. We could explain more but it’s better to know your specific requirements and needs. First, build your own integration blueprint, and we’ll respond with a follow-up phone call or email to review your situation in more detail.

Image courtesy of Flickr, alancleaver

marketing eCommerce , , , , , ,

Introducing Mozu

February 28th, 2014

In September, Volusion, Inc. announced that they were launching a new enterprise-grade eCommerce platform called Mozu. eBridge has been a Volusion partner since 2010 and today we are proud to announce that we have joined the Mozu developers’ program. In the weeks ahead, eBridge will be preparing to build a new connector that will enable Mozu businesses to integrate data between their eCommerce site and their ERP.

We are particularly excited about working with Mozu because we know that it has been designed with back-end integrations in mind. Mozu was created using an API-first approach, which means that eBridge can use the same integration points used by the Mozu web interface. Robust APIs allow us to build strong integrations with the advanced touchpoints that enterprise webstores need. Volusion’s commitment to supporting ‘omnichannel commerce’ is really promising and it speaks to a growing requirement for close coordination between offline retail systems and web-based eCommerce solutions.
You can learn more about Mozu at www.mozu.com or read Volusion’s press release here.

joshbrown eCommerce , ,

Update – ePortal Unscheduled Maintenance Notification

February 28th, 2014

Completion – ePortal Unscheduled Maintenance Notification

Time / Date: 12:00 EST 28 February 2014
***************************  ePortal Unscheduled Maintenance Notification  ************************
Issue: ePortal Maintenance
Start Date: 28 February 2014
Start Time: 12:00 EST
End Date: 28 February 2014
End Time: 12:42 EST
Duration: 42 minutes
Services Impacted: ePortal
Customer Impact: The maintenance window is complete. The ePortal Website and
document processing are functioning as expected.


Contact information:

Email: support@ebridgeconnections.com

Phone: 905-631-8057

Website: http://www.ebridgeconnections.com/support/log-a-case.html

Thank you for selecting eBridge as your provider of business-to-business solutions.

Support Services

eBridge Connections

Toll Free: 1-800-755-6921
Phone: 905-631-8057
Fax: 905-631-8811

Available 24/7 – eBridge now has an online self-serve Knowledge Base packed with tips, trouble-shooting advice, and other current information on your products

Click here to access the online Knowledge Base

PvanAsseldonk Support, The ePortal Web-based Transaction Engine, Uncategorized

Magento 2 Sneak Preview

February 14th, 2014

In December, the Magento product management team hosted a webinar to communicate the progress they have made on Magento 2.0. The webcast lasted more than 2 hours and provided great insight into some of the Magento team’s rationale behind changes in the new product. In this blog post, I’ll summarize a few of the key features that we expect to see in Magento 2.

PHP Upgrade

Magento 1.x is dependent on the server running a version of PHP between 5.2.13 and 5.4. Support for PHP 5.4 was rolled out through a patch in January.

By contrast, Magento 2.0 requires PHP 5.4 at a minimum and it will allow users to upgrade their site to PHP 5.5. PHP has come a long way in the past few years and there are significant performance benefits from running a modern version. On her blog, lornajane has published benchmarks that show the speed improvements between PHP 5.4 and earlier versions of the language.

jQuery by default

In Magento 2, the default JavaScript library has been changed from Prototype to jQuery. This will be a popular decision with many front-end developers. jQuery is a much more common library and using both Prototype and jQuery together could cause conflicts.

Easier Customization and Integrations

The Magento team emphasized that many of the changes in Magento 2.0 are focussed around making it easier for developers to extend and customize Magento.

Mage class replaced with Namespaces and Dependency Injection

The ubiquitous Mage class has been replaced by a new method for declaring class dependencies. You can read more about this on the Magento 2 wiki.

Increased Modularity

In their webcast, the Magento developers said that part of their short-term plan involves decoupling modules and reducing the dependencies between different components of Magento. A goal of this effort is to make it possible for developers to entirely replace a sub-system of Magento with third party functionality.

It will be interesting to see how this can be applied to ERP integrations. There are many overlapping and redundant features between eCommerce systems and ERPs. If the modules can be separated easily then accounting systems might be able to fully replace parts of Magento’s functionality, like inventory management.

Adoption of PSR Coding Standards

The Magento team has committed to following the PSR (PHP Specification Request) coding standards. This is another developer-friendly move that makes perfect sense for Magento to implement now. Magento 2 is already PSR-0 and PSR-1 compliant and PSR-2 compliance is in the works.

Community input welcome

The community is invited to give input on Magento 2 through the Magento 2 Github repo. No release date has been set yet for a production-ready version of Magento 2, however you can download the work-in-progress from Github.

joshbrown Webstore Integration, eCommerce , ,

Integrating Your Salesforce.com CRM With Your ERP Will Make Your Life A Lot Easier

February 10th, 2014

Over the last 2 years eBridge Connections moved their Accounting Integration software to the cloud and with that came a complete overhaul to all of our software adapters. One specific overhaul was our Salesforce.com CRM integration.

Our Salesforce.com integration is one venture that eBridge has put a lot of R&D into. Since moving the Salesforce.com integration to the cloud we’ve been able to expand the capabilities of the integration to fit our customer’s customized demands instead of them having to change their current CRM infrastructure. Our integration allows a Salesforce Opportunity to flow through our universal integration platform and into over 40 supported accounting/ERP packages. We regularly get requests for integration projects with many different ERP systems including, but not limited to, The Microsoft Dynamics family of products, multiple Sage products, SAP Business One, and NetSuite.

The main benefits to our integration with Salesforce.com is that eBridge Connections supports custom fields on all standard objects as well as custom objects to all standard objects, which makes our integration flexible to various different requests.

Since moving the Salesforce.com integration to the cloud we’ve been able to enchance many different integration functions. Enhancements include:

  • Creating and updating Opportunity information in Salesforce
  • Creating and updating Account information in Salesforce
  • Creating a product with Pricebook association in Salesforce
  • Updating product quantity

In the 2 years since we moved our integration to the cloud we have not just strengthened our Salesforce connection, but we’ve  a built strong partnership with CRM company. We are currently featured on their Salesforce.com AppExhange, where you can learn more about our powerful integration software. If you have any questions or comments regarding our Salesforce.com integration specifically or about any CRM integration, feel free to email me directly at pvanasseldonk@ebridgeconnections.com or send us a Tweet @eBridgeConnects.

PvanAsseldonk CRM Integration, Education, Integration, Integration as a Service, eBRIDGE Blog , , , ,

How Are Webstore Customers And Their Orders Posted In Your ERP? Well That Is Actually Up To You!

January 21st, 2014

One of the most common questions we get asked from prospects prior to their integration project starting is ‘How Are Webstore Customers And Their Orders Posted In Our ERP?’ There isn’t just one easy answer to that question and ultimately we’ll post your customers and their orders in a way that’s easiest for you!

We usually break it down to two options:

Option 1- Create a Customer account for every order that is posted in your Webstore, which is done on the fly. If that customer orders again, their Customer Card will be updated in your ERP/accounting system.

Option 2- Post all Web orders under the same Customer Account, which keeps the information being transferred very streamlined. The orders would be posted under your webstore name and when it’s time to create reports you can use their specific email addresses, ship to addresses or bill to addresses as filters. The specific mandatory field you choose for webstore orders will be how each order is recognized by your reporting/ordering.

Determining Factors:

  • If you have a very high volume of orders and you’re receiving 100s to 1000s of customers every day than Option 1 might not be the best option for you. Your ERP must be able to handle all of the orders and information being received
  • If you think posting all the orders under a single account is the best approach then Option 2 is your best choice. You can always do your analysis based a customer’s email or shipping address. This allows for a very slim integration connection because there’s a lot less information being transferred between your webstore and your ERP.
  • If you want to be able to report on all customers and their entire order information, then Option 1 may be your best selection. This option allows you to see each customer’s information in your ERP where you can summarize order information, customer demographics etc., with a more precision than Option 2.

In the end it really depends on how your company operates and how you want to analyze your data. We have many customers using these options as well as some others, but we urge all of our new customers to think thoroughly about this before started any integration. If your company is looking into integration please talk to us so we can help you determine which option may be best for you. If you have any questions regarding posting customers or orders in your ERP from your webstore, please comment below or email me at pvanasseldonk@ebridgeconnections.com

PvanAsseldonk Education, Integration as a Service, Uncategorized, Webstore Integration, eBRIDGE Blog, eCommerce , , , , , , , , ,

Spending Too Much Time Manually Entering Orders From Your Magento Webstore Into Your Accounting System?

December 18th, 2013

Is the number of orders growing and you are hiring people to manually enter orders into your different back-end systems? Is it too time consuming for your business to create a new customer in your accounting system every time a customer orders from your site who hasn’t in the past?

If you answered yes to any of these questions, we may have the solution for you! By integrating your Magento webstore with your ERP or accounting system you can improve productivity, efficiency and accuracy.

To be competitive in today’s online market it is essential for businesses to be quick, responsive and accurate when a customer does a transaction. You don’t want to have dissatisfied customers so the entire online shopping experience needs to be seamless from the front to the back-end of your webstore.

The link below will take you to a recorded version of our Magento webinar which will outline a number of benefits when integrating your Magento webstore with accounting or ERP system which will make your online business more optimized and ultimately more successful.

Seamlessly Connect Your Magento Webstore With Your Accounting Software Webinar: http://www.youtube.com/watch?v=oQMSQSA1mWs

You will learn:

-How a seamless integration will connect your accounting software to your webstore, transferring information like Sales Orders, Customer Info and Inventory
-Different integration options and questions when selling B2B or B2C
-Magento specific tips regarding Catalogue Management, Options for a single Skin compared to Multiple Skins, Group Pricing and More!

If you don’t use Magento, we have a number of upcoming webinars that explain our connections with Volusion, BigCommerce and Salesforce.com CRM, so go to our Webinars webpage if you’re interested!

If you have any comments or feedback regarding our latest webinar, please comment below!

PvanAsseldonk Integration, Integration as a Service, Uncategorized, Webstore Integration, eBRIDGE Blog , , , , , , , , ,

Wow! eBridge Has Reached 100 New Customers In 2013 And We’re Still Going!

December 10th, 2013

eBridge Connections would like to send a special thank you to all of our new customers this year. In the month of December we hit our ‘100 New Customers’ goal for 2013 and we couldn’t be more proud of our hard-working and conscientious Integration Specialist Team!

Our new customers have a wide variety of ERP systems and accounting software, like Microsoft Dynamics, Sage, NetSuite and SAP, as well as many different webstores, EDI Trading Partners and CRM applications, including Magento, Volusion, BigCommerce, Salesforce, Walmart and Home Depot.

But 2013 isn’t over yet – we’ve still got a couple projects in the pipeline. Thanks again to everyone for a fantastic year! We look forward to beating our ‘100 New Customer’ goal next year :)

PvanAsseldonk CRM Integration, EDI Integration, Integration as a Service, Uncategorized, eBRIDGE Blog, eCommerce , , , , , ,

8 Considerations with eCommerce-to-Accounting/ERP Integration

November 28th, 2013
eBridge Connections recently hosted a webinar for eCommerce users who are just starting to look into the possibility of integrating their webstore with their accounting software. We went through what we think are the Top 8 Considerations with eCommerce to Accounting/ERP Integration and we received very positive feedback from those who attended. Since it was so popular with some of out new potential customers we decided to give you a summary of the top 8 considerations plus we’ve posted the recorded version of the webinar on our YouTube channel.
Here are what we think the Top 8 Considerations with eCommerce to Accounting Software are:
1.Know Your Touchpoints
2.Your Approach
3.Type of Business Transactions
4.Know Your Data
5.Walk Through Your Process
6.Clarify Your Inventory
7.Balance Duplicate Data
8.Define Your Integration Team
If you would like more info please watch the full 20 minute webinar by following this link: http://youtu.be/j2qWEnqIPXc Let us know if you have any questions or comments regarding the webinar!

PvanAsseldonk Integration, Integration as a Service, Uncategorized, Webstore Integration, eBRIDGE Blog ,

EDI and Healthcare.gov

November 23rd, 2013

The technical glitches of healthcare.gov, America’s new insurance marketplace have been widely reported in the news. Some of the problems stem from the EDI transmissions used by healthcare.gov to communicate enrolment data to health insurance providers. In this post, I’ll describe the EDI transmissions used by the new marketplace and summarize a few of the problems that cropped up.

There are two types of EDI documents in use with the new marketplace: 834s and 999s. “834” is an EDI code that refers to a benefit enrolment and maintenance document. When a shopper on healthcare.gov chooses an insurance plan, the marketplace is designed to send an 834 to the insurance provider selling the user’s selected plan. This document contains information like the user’s name, their address, their phone number, their spouses or children on the plan and other details that the insurer needs to complete the enrolment.

Once an insurer receives an 834 from healthcare.gov, they respond with another document called a 999. 999s are an acknowledgement that the provider received the 834. The 999 tells healthcare.gov that the 834 was accepted by the insurance provider, that it was rejected or that it was accepted with errors. When the user pays their first premiums, the healthcare provider sends an 834 to healthcare.gov to confirm that the customer completed their enrolment. The marketplace responds with a 999 to acknowledge the insurer’s 834.

These EDI transmissions are backed up by an translator that converts the data into XML, a format that the marketplace’s systems can read. The Center for Medicare & Medicaid Services (CMS) has published an diagram that shows how this all works:

Healthcare.gov went live on October 1. At first, there were technical problems unrelated to EDI and very few people were able to enrol in plans. However, meeting minutes show that EDI problems quickly became apparent as the marketplace began to work properly. In a meeting on October 8th, administrators noted that “Issuers are not receiving 834s when they should be.”
An EDI dashboard was created to monitor the success rate of transactions, however the dashboard did not provide cumulative data. Again, this is described in the meeting notes from October 8th:
“News websites are reporting issuers who say they are receiving flawed 834s; because we use a daily dashboard, it is hard to see the cumulative number of 834s sent out that we don’t have a response back for.”
They added that: “There were 700+ enrollments last night. There are 300+ failed 999s”.

Other EDI problems that were reported after go-live included duplicate 834s, 834s with incorrect relationships — for example, one man was reportedly recorded as having three spouses — and 834s that lacked important information, like county codes. In some cases, the minutes show that issues that were identified through EDI may have been rooted in upstream components of the marketplace, like the XML provided to the EDI translator.

In hindsight it is easy to say that extra testing would have been beneficial for healthcare.gov before it went live on October 1. It seems like it was especially challenging for administrators and insurers to resolve EDI problems after the website had already been launched. You can read more about the EDI issues with healthcare.gov on the Washington Post blog and here at CNN.com.

joshbrown EDI Integration, General EDI , , , , ,