dotConnect for BigCommerce: Query Your Store's Catalog and Orders With SQL From .NET
dotConnect for BigCommerce is a $339.95 ADO.NET data provider from Devart that lets C#, VB.NET and F# applications read and write a BigCommerce store's products, variants, customers, orders, carts and price lists as if they were database tables, using SQL or Entity Framework Core instead of hand-written REST calls. It runs on .NET 5 to 11 and .NET Framework 4.5 to 4.8, on Windows, Linux and macOS. The price is a perpetual developer license with a year of updates.
If you've ever written paging loops, rate-limit retries and JSON models just to copy BigCommerce orders into an ERP every night, this is the shortcut: SELECT from Orders, UPDATE Products, and let the provider turn it into API requests.
Quick facts
- Version: 3.3.248, released November 11, 2026 (.NET 11 and EF Core 11 support)
- Developer: Devart
- Data source: BigCommerce stores, through BigCommerce API v3 or v2
- Authentication: OAuth with Store Id, Client Id and Access Token, or the legacy Basic method with API path, user name and authentication token
- .NET: .NET 5 to 11, .NET Core 2.0 to 3.1, .NET Standard 2.0/2.1, .NET Framework 4.5 to 4.8, ASP.NET Core, Blazor, .NET MAUI
- ORMs: Entity Framework Core 1 to 11, Entity Framework 4 to 6, Dapper, NHibernate
- Package: Devart.Data.Bigcommerce and Devart.Data.Bigcommerce.EFCore on NuGet. The Windows installer is 16.61 MB
- Price: Developer $339.95, Server $799.95, OEM for 10-100 devices $4,999.95, each a perpetual license with one year of updates and support
- Trial: full product for 30 days, no credit card, free Devart account needed
- Refunds: within 30 days if a technical issue stops the provider from working and Devart support can't resolve it
- What we checked: version 3.3.248 and the 16.61 MB size on the download page, the revision history back to 2019, the connection-string reference and the API v2/v3 object lists in Devart's documentation, and the order page on November 14, 2026: $339.95 for the default single-developer license, $799.95 for Server and $4,999.95 for OEM for 10-100 devices. We didn't install it or connect it to a BigCommerce store.
Download Free TrialBuy Now
Overview
BigCommerce only offers REST APIs, and they come in two generations. The newer v3 API covers the catalog (products, variants, modifiers, price lists, metafields), while orders and many other resources still live in the older v2 API. Any integration ends up juggling both. dotConnect for BigCommerce hides that split behind one connection: you choose API Version v3 or v2 in the connection string, and objects that v3 doesn't cover are still fetched over v2 automatically.
Under the hood, a simple query such as SELECT id, name, price FROM Products is translated straight into an API call. A query with joins or conditions the API can't filter on is split: the provider fetches what it can from BigCommerce and its local SQL-92 engine does the rest. The classes follow ADO.NET (BigcommerceConnection, BigcommerceCommand, BigcommerceDataReader, BigcommerceDataAdapter), so the code looks like database code.
The provider's first release was in February 2016. The revision history shows how it has caught up with BigCommerce: OAuth and the API version choice in the connection dialog (January 2025), interactive OAuth at runtime (December 2025), a CustomerMetafields object and a ProductImageContents object for image binaries (May 2026), and a metadata fix for the cart objects (September 2026).
Visual Studio's Add Connection dialog for the BigCommerce data source: Store Id, Client Id and Access Token, Authentication Type OAuth and API Version v3, with C# connection code behind it.
Features
The BigCommerce catalog as tables
dotConnect for BigCommerce exposes the v3 catalog as Products, ProductVariants, ProductVariantOptions and their values, ProductModifiers, Brands, Categories, ProductImages, ProductVideos, ProductReviews, ProductCustomFields, ProductsBulkPricingRules, complex rules, PriceLists and PriceListRecords, plus Brand, Category, Product and Variant metafields and a CatalogSummary. On a v2 connection you get the older shapes instead: ProductSkus, OptionSets, Options, ProductRules, ProductConfigurableFields and ProductGoogleProductSearch. The table set depends on which API version you pick, so choose before you build your queries.
Orders, customers and carts
dotConnect for BigCommerce also reaches the store's transactional data, which BigCommerce serves through its other APIs: orders and OrderShipments, Customers, CustomerAddresses, CustomerGroups (with their discount rules), customer custom fields and metafields, and the cart objects (CartLineItems, CartCustomItems, CartGiftCertificateItems, CartMetafields). Full SELECT, INSERT, UPDATE and DELETE are supported where BigCommerce allows them, and a Readonly connection option limits a connection to SELECT, which is a sensible guard for reporting code.
Custom fields and image binaries
dotConnect for BigCommerce has a Use Custom Fields option that adds a CustomFields column to Products on v3 connections, so product custom fields come back in the same row instead of a separate query. ProductImageContents returns the binary content of product images, handy for exporting a catalog with its pictures.
Entity Framework Core and other ORMs
dotConnect for BigCommerce ships a separate EF Core package, so you can scaffold a DbContext from the store and write LINQ against Orders and Products. It also supports Entity Framework 4 to 6, Dapper and NHibernate. Devart's Entity Developer, a visual model designer sold separately, can build the model for you.
Entity Developer's Create Model Wizard with Devart dotConnect for BigCommerce as the provider and its Connection Editor open. The model diagram in the background is a sample model, not BigCommerce data.
Bulk loading, tracing and Visual Studio tools
dotConnect for BigCommerce includes a BigcommerceLoader component for loading many rows at once, paged access to large result sets, and a BigcommerceMonitor component plus Devart's dbMonitor to see the requests your SQL produced. In Visual Studio 2015 to 2026 it adds Server Explorer browsing of the store's tables, design-time components and SQL completion in its editors. VS Code and Rider work too, without the design-time parts.
Benefits
- One code style for every data source. If the rest of your app talks to SQL Server through ADO.NET or EF Core, the BigCommerce code looks the same.
- Less API plumbing to maintain. Paging, authentication and the v2/v3 split are the provider's problem, not yours.
- Ad-hoc questions get easy. "Which customers ordered product X last month" is a join, not a script.
Real-World Uses
- Order sync to an ERP or warehouse system. A scheduled .NET job selects new Orders and pushes them to the warehouse database with plain ADO.NET.
- Bulk price updates. Merchandising sends a spreadsheet of new prices, and one UPDATE per row on PriceListRecords applies them to a B2B price list.
- Catalog export with images. A tool joins Products, ProductVariants and ProductImageContents to build a supplier feed or a print catalog.
- A webhook handler. When BigCommerce calls your endpoint about a new order, the handler reads the full order and customer record before deciding what to do. A Devart forum user described exactly this use in 2018.
Who It's For, and Who Should Skip It
It's for .NET developers and integration teams who connect BigCommerce to internal systems and would rather use SQL, ADO.NET or EF Core than the REST API. It pays off most when the integration touches many object types or changes often.
Skip it if your integration is one endpoint, such as reading new orders: a few HTTP calls cost nothing. Skip it if you're not writing .NET code: Devart sells an ODBC driver, an Excel add-in, a Python connector and an SSIS component for BigCommerce, and no-code tools exist too. And if a sync needs real-time event handling at high volume, the provider still makes REST calls under the hood and is bound by BigCommerce's API rate limits.
Usage Guide
- In the BigCommerce control panel, create an API account for your store and note the Store Id (from the API path), the Client Id and the Access Token, giving it only the scopes your app needs.
- Install dotConnect for BigCommerce from the Windows installer (free Devart account) for Visual Studio integration, or add the Devart.Data.Bigcommerce NuGet package to your project.
- In Visual Studio's Server Explorer, choose Connect to Database, pick BigCommerce Data Source, and enter the OAuth values with API Version v3. Test the connection and browse the tables.
- In code, open a
BigcommerceConnection with a connection string like Authentication Type=OAuth;Store Id=...;Client Id=...;Access Token=..., then run SQL through BigcommerceCommand.
- Before deploying, add the license key (the LoadLicenseKey method or the License Key connection string parameter) so the app runs outside your development machine.
Before you buy
- The Developer license covers one developer's workstations. Running the app on a shared server needs the Server license, and shipping it to customers needs OEM. The Buy Now button opens the order page with the single Developer license selected, and you switch edition, term (1, 2 or 3 years of updates) and premium support there.
- All licenses are perpetual: the version you have keeps working after the update year ends.
- Devart's ordering FAQ grants refunds within 30 days when a technical problem can't be fixed by support, so test against your own store during the trial.
Where it falls short
- Two object models. Products, options and SKUs look different on v2 and v3 connections, so code written for one won't work unchanged on the other.
- SQL over an API isn't a database. Joins and filters BigCommerce can't do server-side are done locally after fetching, which can mean many API calls on large catalogs.
- Older documentation. The getting-started connection walkthrough still describes the legacy API account (API path, user name, token) rather than OAuth, so use the connection-string reference for current options.
- History of lagging .NET support. In 2018 Devart told a forum user the provider didn't support .NET Core at all. That's fixed (NuGet with .NET Core support since November 2023), but it shows that new platforms can arrive later here than in Devart's database providers.
What Users Say
There are no rated reviews of the BigCommerce provider on the big review sites. The public record is Devart's forum for its cloud ADO.NET providers.
Devart forum, December 2018 to January 2019
A developer (jgoemaat) explained his plan: "I simply want to pull some customer and/or order data from BigCommerce every time I receive a new order web-hook call from them." He asked whether it would run in Azure Functions on .NET Core and how licensing would work there.
Devart's answer (Shalex, Site Admin) was frank: ".NET Core is not supported by this provider," but the trial could be tested on Azure, and the web-site licensing approach applied. The user pushed back: "Do you have any plans to support .NET Core in any future release? I could see you selling licensing for your dotConnect products to a lot of Azure Function developers as it gains steam."
Devart replied it would investigate .NET Standard 2.0 support, and in January 2019 reported that "the bug with using ASP.NET Core Web Application (.NET Framework) and Azure Functions v1 (.NET Framework) projects in Visual Studio 2017 is fixed in v1.7.822."
Two things stand out: Devart's staff respond in the forum and ship fixes, and the user's request was eventually met, since the provider now runs on .NET 5 to 11 and .NET Core through NuGet. Reviews of Devart's dotConnect line as a whole on G2 and Capterra tend to praise the support and Visual Studio integration and criticize the price and documentation, which matches what you'd expect here.
Comparisons
vs. calling the BigCommerce REST API yourself
Direct API calls with HttpClient cost nothing and give you every endpoint the moment BigCommerce ships it, including ones the provider hasn't mapped yet. The provider saves you the models, paging and v2/v3 bookkeeping, and gives you joins and EF Core. For a handful of calls, go direct. For an integration that touches the whole store, the provider earns its price.
vs. Devart's ODBC Driver for BigCommerce
The ODBC driver gives the same SQL access to tools that speak ODBC, such as Power BI, Excel and SSIS, and to non-.NET languages. dotConnect is the better fit inside a .NET application because of its native ADO.NET classes, EF Core support and Visual Studio integration.
Editions and Pricing
Every edition has the same features. They differ in where you may install and distribute the provider, and all are perpetual with one year of updates and support.
| Edition | Price | Who it covers |
| Developer (default on the order page) | $339.95 | One developer, on one or more development workstations |
| Server | $799.95 | One server (web, application or batch) used by one organization |
| OEM for 10-100 devices | $4,999.95 | Redistribution with your own application |
| Site and OEM for 100+ devices | On the order page | Unlimited computers in one company, or larger redistribution |
FAQs
Does dotConnect for BigCommerce work with OAuth API accounts?
Yes. dotConnect for BigCommerce supports Authentication Type OAuth with your Store Id, Client Id and Access Token, and since version 3.0 also interactive OAuth at runtime. The older Basic method with a legacy API path, user name and token is still available.
Should I choose API v3 or v2 in dotConnect for BigCommerce?
dotConnect for BigCommerce uses v3 for the catalog objects it supports and falls back to v2 for everything else, so v3 is the natural choice for new projects. Pick v2 only if existing code relies on v2 objects like ProductSkus or OptionSets.
Can dotConnect for BigCommerce run in Azure Functions or Linux containers?
Yes, today it can. dotConnect for BigCommerce ships as a NuGet package for .NET 5 to 11 and .NET Core on Windows, Linux and macOS. The 2018 limitation to .NET Framework no longer applies.
Can I make a dotConnect for BigCommerce connection read-only?
Yes. dotConnect for BigCommerce has a Readonly connection string option that allows only SELECT statements, useful for reporting or analytics code that should never change the store.
Do I need the Server license for a web app that uses dotConnect for BigCommerce?
Usually yes. dotConnect for BigCommerce's Developer license is for development and testing by one developer. Deploying to a web, application or batch server used by your organization is what the Server edition covers.
Does dotConnect for BigCommerce work with a proxy?
Yes. dotConnect for BigCommerce has Proxy Host, Port, User and Password connection options, and connects over SSL/TLS.
System Requirements
- .NET 5 to 11, .NET Core 2.0 to 3.1, .NET Standard 2.0/2.1, or .NET Framework 4.5 to 4.8 (the installer needs .NET Framework 4.0 or later, and TLS 1.2 needs 4.5)
- Windows, Linux or macOS, x64 or x86
- Visual Studio 2015 to 2026 for design-time features (not in Express editions)
- A BigCommerce store and an API account
Conclusion
dotConnect for BigCommerce is worth $339.95 to a .NET team that maintains a real BigCommerce integration, like order sync, catalog management or reporting across many object types. The one reason to buy it is that the store becomes a SQL data source your existing ADO.NET and EF Core code can use, with the v2/v3 API split handled for you. The main reason not to is scale of need: a small, single-purpose integration is cheaper to write against the REST API, and a server deployment means the $799.95 Server license, not the Developer one. Test it on your own store during the 30-day trial.
Download Free TrialBuy Now