Lonnie,

Thanks so much for this feedback. I have forwarded this request to our development team so that they are aware of your interest. Keep the feedback coming - and be sure to "follow" this thread for possible future updates.

any updates on this?  I would like to be able to just send shipping info to shipping easy as well to utilize all of the shipping features, and tracking , emails, online status etc, but pack in a different software hooked to my inventory system which doesn't use API?

Hi Casey, 

Thanks for checking in! Unfortunately, we do not yet support ODBC but we do have an Open API. Here's a bit more info: ShippingEasy's Open API

We'll update this thread should we have any updates on ODBC support though. 

Thanks again!

Thanks Rachael,  I think you missed the point of my post.  My inventory system does not use API.  I have an on-premesis ERP system which is oracle based and can only use ODBC and Flat Files,  I already know the FlatFile capabilities but that's clunky and will require a lot of custom programming to pull data from the oracle database which is already configured for ODBC.   

I get it if there is not a lot of need for this, but maybe there are some others who could use this functionality? 

My 2c (again). We use the CSV import to import our website orders into SE so that we can use SE to ship and track ALL our internet orders. But Casey Whitcher is correct, this is clunky. An ODBC connection is a universal standard for send/receive data between disparate databases, and it would be oh-so-nice if SE would support ODBC. The only shipping software out there that I've used that supports ODBC is Iabol, but their interface is clunky and ShippingEasy's capabilities far surpass what they do.

Hey Lonnie,  True ship is actually using it now with with a plug in that they don't really like for $150, but they have an old version of trueship that uses it natively, then they have a new version coming out in a couple months that will use it natively too.  

But... I don't think TrueShip in it's current state does half what SE does so it's not on my list.

However, in my case, my ERP actually has really good scan packing features, but the pick lists are lacking, also the ERP uses 4 locations which change often by warehouse staff.

For now, we are going to just print pick tickets and pack in the ERP but ship in SE to get the cloud features, and Cubic rates, I'd love to move to doing picklists in SE, but we will always pack in our ERP because it has the basic scan packing by item sku when the items packed,

So sorry for the miscommunication, Casey - it looks like I misunderstood and missed that bit of info. May I ask what inventory solution you are using that uses ODBC?

I've added your request to our running list of features to consider. However, we don't have much feedback to date on using ODBC systems with ShippingEasy. We've found that most of our customers who need to integrate a system other than our supported integrations can use ShippingEasy's open API. In other words, we'll need to learn more about our customers' needs in an ODBC integration before prioritizing it for development. 

It's great to see more interest and feedback - thank you Lonnie! We'll continue to monitor this thread, and our other channels, to learn more about your needs. As we have questions or slate anything for development, we'll post updates here as well.

Casey, I forgot about Trueship, we used them years ago too. But we are in the same opinion that SE's cloud features and scale/printer support and integrations and workflow are much better. It's just that the cloud features are not only a strong point, but also a weak point, because tons of businesses have internal ERP softwares that use ODBC, and it doesn't seem there's any company that is combining all these features in one package.

Hi all - After speaking with our developers some, I wanted to post another update. 

ODBC is a way to "talk" to databases. Because everyone's databases are different, building an integration entails creating custom code to adapt each ODBC customer to our API. Any other software provider (especially cloud based) would be in a similar situation, which is likely why there aren't many solutions available to integrate with ODBC. This is also another reason why we provide an Open API.

While not all systems may be able to access an API, in many cases it's possible to create code to bridge that gap between the API and database. In other words, before connecting to the Open API, you would need to write a program to create your own "Open API" access to your database. Then connect the two APIs together. It is a second step required to complete the connection, but it's the best option currently available with our Open API.

If we can find that many of our customers are using the same ODBC and database configuration, we may be able to consider building an integration.

In any case, we'll keep an eye on this thread. Please continue to post details about your configuration and any specific software that you use.

No updates on this? Would be great if there was an ODBC connection available for us. If the connector would provide R/O access to retrieve the orderid, customer shipping address, and the costs associated with the shipment and carrier/tracking number, it would be very helpful.

Been downloading CSV files almost every day now for a couple of years, and it sure gets old.

After reviewing Jennifer's comment from a couple of years ago, I think they may be looking at it wrong. ShippingEasy (SE) should NOT CARE what database the customer uses, they should only look at the connection FROM their (SE) database. The customer exports the data using ODBC (from SE), then worries about how to put it into their (customer) database through custom code, a different ODBC connection, etc. SE doesn't need to have anything coded for each customer, as THAT is the point of ODBC, it is a general data connection to a specific database.

As customers, we pull the data from ShippingEasy, then WE take care of how to push it into other applications.

Hi Jim,

Thanks for posting to our forums! It sounds like you are only interested in pulling data from ShippingEasy via ODBC. 

It looks like this thread was started as a request for importing orders from ODBC into ShippingEasy instead, which Jennifer's comment would be relevant to.

Would you consider starting a new feature request thread specifically for exporting information via ODBC? That way we can get an idea of how many people would be interested in just an exporting option.

Thank you!

Thanks, just suggested it: ODBC Export Shipping Data