Forem: BigCommerceDevs

Recap: Multi-Location Inventory Ask Me Anything

katie hoesley — Mon, 13 Feb 2023 19:45:26 +0000

If you missed our recent MLI (Multi-Location Inventory) and BOPIS (Buy Online Pickup In-Store) Ask Me Anything session in our Developer Slack space, don’t worry! I’ve compiled all questions and answers from the AMA in this blog.

Buy Online Pickup In Store (BOPIS), also known as Click & Collect outside of the United States, is a frequently requested feature for enterprise merchants. In order to enable BOPIS, we have transformed our platform from being able to support inventory stored at a single location out-of-the-box, to being able to support multi-location inventory (MLI).

Our engineers have developed a suite of APIs that will enable agency partners, tech partners, and eligible merchants to build custom BOPIS experiences via BigCommerce APIs. More specifically, we’ve released 3 new APIs (Inventory, Locations, and Pickup Methods) and updated a number of existing APIs to support BOPIS experiences.

After reading the summary, if you still have questions, please reach out to me. Let’s dive into the AMA!

The Hosts

During this AMA, your burning MLI and BOPIS were answered by a few of BigCommerce’s subject matter experts:

Jordan Sim, Senior Director of Product Management | “I’ve been with BC since 2013. Over my 10 years, I’ve worked in and/or led teams across most, if not all, areas of our commerce platform. I’m passionate about delivering valuable solutions and seeing our partners and merchants succeed in the market.”

Christine Truong, Program Manager for MLI | “I’ve been with BigCommerce for 3 years and have worked in Cart & Checkout, Orders, Promotions, Shipping, and Tax domains. I took over the MLI Program in 2021, and I provide support to Product, Engineering, and Design, while ensuring the delivery of all the projects under this program.”

Vadim Borinski, Engineering Manager: Shipping & Tax, Pricing | “I’ve been with BC since 2013, and most of my time has been spent in the Shipping space. Recently I’ve started looking after Pricing as well and over the last few years, I’ve been leading our MLI program from an engineering perspective. I don’t write as much code as I used to (or would like to) but I do love solving problems for our users.”

The Questions & Answers

I have a client that does BOPIS today. His #1 complaint is around sales tax. His physical store is in the Kansas City, Missouri area and is frequently visited by people from both Missouri and Kansas When people from KS order online and then pick up in the store (in MO), the sales tax is not correct. Seems the issue is Checkout does not do anything related to the shipping address when customers select “pick up in store” as the shipping method. Does this ring a bell for anyone?

Jordan Sim: Thanks for submitting the first question!

As you correctly stated, today, i.e. before the MLI BOPIS APIs, merchants have been able to repurpose static shipping methods and rename them to creatively render a pickup method within Checkout.

So technically, the data is formatted in the shape of a shipping method, but it’s really pickup data that’s been shoe-horned in. More specifically, the pickup in-store method that they are displaying is really just a text label.

With this MLI BOPIS API release, we will be formally introducing a new concept called Pickup Methods. These are aware of the location and the BigCommerce tax engine (and integrations with tax partners, like Avalara) can consume this location data where the order is being picked up to calculate the right sales tax.

Related to BOPIS, one of my clients who is located in the Kansas City area told me this:

“Right now the more common issue is that people from well outside the KC area from Florida to Oregon are selecting Pickup in Store for their shipping preference. If when they selected Pickup in Store it showed the store address or made them pick a location (if more than one store exists) the problem would probably be dramatically reduced.”

Jordan Sim: This experience is all possible when you consume the MLI BOPIS APIs as you can build this experience in your own custom checkout.

Are there plans for a basic front-end implementation of BOPIS out-of-box in the future, or is the desire to keep this as an API suite for users to build with?

Jordan Sim: There are plans for a basic front-end implementation of BOPIS in the future, for both the reference theme (Cornerstone) and the default checkout that comes out of the box. The timeline is TBD.

When is the feature going live to the public?

Jordan Sim: We intend on launching this (in terms of general availability) within 1H’23. We’re currently working through Open Beta feedback — and the volume and criticality of the feedback we receive will determine how quickly we can make this generally available!

Where can we find documentation on changes/UI updates to the BigC Control Panel related to orders that are placed with a BOPIS shipping method selected?

For example, we are most of the way through a BOPIS implementation, and after sending data into the new endpoints, we noticed a new Location line appear in the order details. This is awesome! But we had to “accidentally find it” and are now wondering what other things “appear” on other screens throughout the Control Panel, and what all the “Possible UI Elements” are so we can be sure we have created all of the expected data in this new API.

Christine Truong: The support KB documentation will be updated in advance of the general availability date within 1H’23. For more context, we have updated multiple UIs to enable BOPIS within the control panel to support an end-to-end experience. It looks like you’ve already discovered one of them, i.e. in Orders. We are introducing new UIs (to enable Locations Management and Pickup Methods Management) and updating existing UIs (i.e. Orders and Catalog)

Is there a plan/timeline to more elegantly handle returning Shipping Options from a store with BOPIS enabled?

In our current implementation, all products in a cart still needed to be consigned (attached to an address) before Shipping Options are returned from BigC. This makes no sense in a BOPIS scenario. By definition, the customer’s intent is to pick the item up in-store, so making them supply a shipping address only to select pickup is very counter-intuitive.

Christine Truong: Great question! Yes, we will be handling this elegantly with this release of the MLI BOPIS APIs.

As you correctly stated, today, i.e. before the MLI BOPIS APIs, merchants have been able to repurpose static shipping methods and rename them to creatively render a pickup method within Checkout. So technically, the data is formatted in the shape of a shipping method, but it’s really pickup data that’s been shoe-horned in.

With this release, we will be formally introducing a new concept called Pickup Methods. Here you can create one or multiple pickup methods per location (e.g. In-store pickup and Curbside pickup).

And rather than shoe-horning in the data, the data will be represented as consignment type pickup, which is different from shipping, which has a different consignment type. This creates a clean design and data separation.

Are there any plans for a BigCommerce Control Panel UI to edit BOPIS Location details? If so, what is the projected timeline for that? (We are trying to plan for what tooling we need to build and if it is worth the effort).

Jordan Sim: Yes there are plans for a BigCommerce Control Panel UI to edit BOPIS Location details! We want to launch a beta of the UIs, this month, in February. This will allow you to modify BOPIS location details. So sit tight and save your efforts on tooling because this is coming your way shortly.

Regarding the limit to the number of locations that can be enabled via the API, and how it is raised: How can a merchant or partner request to create more than 4 locations for their store?

Jordan Sim: This will be available to merchants only on the ENTERPRISE plan or PARTNER SANDBOXES (who are building staging environments to test/build new sites). If you’re on the Enterprise plan, please reach out to your Account Manager letting them know how many locations you are looking to support and they’ll route the request internally to the appropriate team.

Are there any prerequisites that must be met to request more than 4 locations (for example, can the limit only be overridden for ENT and Partner stores)?

Jordan Sim: I’ll cross-link to this post which I believe will answer this question: https://bigcommerce-devs.slack.com/archives/C04LGFKLU3X/p1675294052278289?thread_ts=1674853811.195559&cid=C04LGFKLU3X

In regards to a checkout, can I checkout with 2 items in the cart where 1 item is purchased from one location (store) and another one is from another location? After successful checkout, the inventory should be deducted from different representing locations (stores).

Jordan Sim: Today, this is not possible and this is an intentional design decision. The majority of BOPIS transactions worldwide are single pickup locations only per order. A very small percentage of orders are picked up at multiple locations.

Therefore taking an iterative release approach we supported a single pickup location per order in the first release of BOPIS. In the future, we will look to support more sophisticated use cases like the one you have shared.

Will Multi-location Inventory and BOPIS be available to all plans?

Jordan Sim: Yes! MLI and BOPIS will be available to all plans.

In addition to this, we intend on launching this (in terms of general availability) within 1H’23. We’re currently working through Open Beta feedback — and the volume and criticality of the feedback we receive will determine how quickly we can make this generally available!

Will the “Partial Pickup” on a single location will be supported on the first version of BOPIS? For example, if a customer picks up one product on a day, and on a later date (at the same location) they pickup the rest of the items in his order. Will that be possible to do in the Order Admin view?

Jordan Sim: Partial Pickup of a single order from a single location will not be supported on the first version of BOPIS. In this first release of the MLI BOPIS APIs, we allow the shopper to pick up the whole order atomically, or not. The reason for taking this is because, from the initial merchant and partner research, we learned that the majority of the time, shoppers completely pick up their order in total. We do, however, want to support partial pickups for a single order from a single location in the future.

Will this be available for BigCommerce B2B Edition customers as their checkout is customized?

Jordan Sim: Yes — All your need to do is upgrade the CheckoutSDK to the latest version to get access to BOPIS. Once you do this, you will have access to the APIs that’ll allow you to customize the B2B Edition Checkout to support the BOPIS experience.

Reading through the catalog API info, “Once you update to consume the new Inventory API, management of inventory via the Catalog API will cease. All inventory management will occur through the Inventory API.”

As a Tech partner (App) that currently reads inventory_level from the product catalog, how do I know a store has switched over to the inventory API? Is there going to be a new feature in the Get Store Information API call to know where I have to read inventory for a store?

Vadim Borinski: In the short term you will still be able to read an inventory level* from the product catalog however we do discourage this as there may be some delay in syncing values — and we do intend to completely remove inventory data from the Catalog API in the long term.

More importantly, the catalog API inventory level will always represent the stock level at the default location, so you will lose visibility into stock levels at other Locations (assuming you use more than one).

Finally, yes, we do plan to add a way to indicate whether MLI is enabled or not for a store likely in time for GA.

That’s it!

And that’s a wrap on our MLI/BOPIS AMA recap! Huge thanks to Christine, Vadim, and Jordan for participating in this AMA and answering so many burning questions from our Developer Community.

If you’re a developer and build on the BigCommerce platform, join our BigCommerce Developers Slack community by applying here!

If you still have questions and this blog doesn’t answer them, reach out in our Developer Slack space, comment on this blog, or tweet at us (@katie_hoesley or @BigCommerceDevs)

Connect With Us!

BigCommerce Developers Community Update: We’re On Youtube!

katie hoesley — Fri, 10 Feb 2023 20:59:06 +0000

BigCommerceDevs YouTube is LIVE!

If you’ve been patiently waiting for BigCommerce Developers to start our own YouTube channel, you’re in luck!

Last week, we debuted our channel and our first video series, “Getting Started with BigCommerce”, filmed and edited by our Developer Advocate Stephen Hilliard.

This is our first series, with many more coming your way! We hope our YouTube page becomes a helpful, informative resource for any developers building apps, widgets, storefronts, and anything else on BigCommerce’s platform.

What Do We Need From You, the Developers?

In a word: feedback!

These videos are one of our initiatives toward making BigCommerce the absolute best eCommerce platform for developers. We’d love to hear your thoughts on the videos, the types of videos you’d like to see, and anything in between.

These videos are for you, our developer community, and we hope we can continue our video initiative by listening to and implementing your input.

What’s Next?

Head on over to our new YouTube page, subscribe, and stay up-to-date on the videos we’re posting.

We’ll continue to create video content, and if there’s a specific topic you’d love a video or series on, comment on this article, email us at devrel@bigcommerce.com, or tweet at us!

Wallet Buttons on Product Detail Page

Stephen Hilliard — Mon, 09 Jan 2023 17:38:33 +0000

Wallet Buttons are now available on Product Detail Page with PayPal / Braintree yellow button & PayPal / Braintree Venmo! With Amazon, Apple, & Google Pay coming later in 2023!

As ecommerce methods change, so will we for the best possible platform experience. As of March 31, 2021, 30% of payments at the checkout come from digital wallets. From this, 50% of digital wallet payments come from a mobile device. With an upward trend in checkout conversions using digital wallets especially on mobile devices the platform is moving away from having the shopper to sign-in and towards the use of wallets/alternative payment methods.

These wallet buttons on the Product Detail Page, or PDP will enable customers to click the wallet. Rather than add-to-cart, to checkout that item with the wallet provider. This will create the opportunity to optimize for guest checkout by having the wallet buttons (also referred to payment buttons) at the product page.

What this Means for you:

One valuable outcome is speeding up the payment process where shoppers won't have to fill-in all the details on the checkout page. Another business benefit is optimizing the use of wallet buttons on the platform.
Provide merchants with the option to place wallet buttons on the product detail page as well as the option to configure the look (where applicable) of the buttons.
Provide system integrators and merchants with the option to add payment buttons to headless stores.
Merchants can easily configure the product page to have buttons without needing to write any custom code themselves.

I’m interested! What are my next steps?

The file structure of each theme can be unique; therefore, some knowledge of Stencil development may be required to render wallet buttons. Cornerstone 6.7.0+ supports wallet buttons by default; however, you can upgrade older themes to support wallet buttons by following the steps outlined in this article: (Disclaimer: Amazon/Apple/Google pay are mentioned in this article and documentation but will not be available till later in 2023)

Add wallet buttons feature to the theme settings:

To start working with wallet button implementation extra config updates should be added to the theme settings.
First of all we should make an ability to turn on / off the feature for the merchant. To make pay it possible we should add show_quick_payment_buttons configuration with default value to the config.json file and make an update to the schema.json file to create a checkbox for toggling the feature in Page Builder.

Adding show_quick_payment_buttons configuration with default value:
config.json

{
  ...,
  "settings": {
    ...,
    "show_quick_payment_buttons": true
  }
}

To make it turned on by default set "show_quick_payment_buttons": true.

Adding checkbox to Products section for toggling the Wallet buttons feature in Page Builder:

schema.json

{
  ...,
  {
    "name": "Products",
    "settings": [
      ...,
      {
        "type": "checkbox",
        "label": "Show quick payment buttons",
        "force_reload": true,
        "id": "show_quick_payment_buttons"
      },
      ...,
    ]
  }  
}

It should look like:

This settings option is responsible for providing an array of data to the theme.

Add an ability to set how many wallet buttons should be always visible on product page:

This option is responsible for a quantity of wallet buttons what should be always visible on the product page.

Adding paymentbuttons-number-of-buttons configuration with default value:
config.json

{
  ...,
  "settings": {
    ...,
    "paymentbuttons-number-of-buttons": 1
  }
}

Info: if the settings option is not provided, then only one button will be shown by default. The customer will have an access to another buttons by clicking on “More payment options“ button.

Adding base wallet buttons count section to the Page Builder into Payments section:
schema.json

{
  ...,
  {
    "name": "Payments",
    "settings": [
      ...,
      {
        "type": "heading",
        "content": "Quick payment buttons"
      },
      {
        "type": "select",
        "label": "Number of buttons always visible",
        "force_reload": true,
        "id": "paymentbuttons-number-of-buttons",
        "options": [
          {
            "value": 1,
            "label": "1"
          },
          {
            "value": 2,
            "label": "2"
          }
        ]
      },
      ...
    ]
  }  
}

It should look like:

Add sorting for the wallet buttons:
Merchants can have an ability to choose an order for rendering wallet buttons. To add sorting feature theme setting config should be updated.

Info: The default sorting is PayPal/BT button, ApplePay, GooglePay, AmazonPay, Venmo. There are 2 buttons displayed max and 4 buttons upon clicking "Show More", but the 5th button is not visible at all. Merchants can move the 5th button to the top of the list to make it visible.

Adding paymentbuttons-provider-sorting configuration with default value:
config.json

{
  ...,
  "settings": {
    ...,
    "paymentbuttons-provider-sorting": []
  }
}

Adding sorting wallet buttons component to the Page Builder into Payments section:
schema.json

{
  ...,
  {
    "name": "Payments",
    "settings": [
      ...,
      {
        "type": "heading",
        "content": "i18n.QuickPaymentButtons"
      },
      {
        "type": "sort",
        "label": "i18n.ProviderSortingOrderLabel",
        "id": "paymentbuttons-provider-sorting",
        "force_reload": true,
        "options": [
          {
            "value": "paypal",
            "label": "i18n.PayPalProviderSortingLabel",
            "enabledBy": "paypal"
          },
          {
            "value": "paypal-credit",
            "label": "i18n.PayPalCreditProviderSortingLabel",
            "enabledBy": "paypal-credit"
          },
          {
            "value": "paypal-venmo",
            "label": "i18n.PayPalVenmoProviderSortingLabel",
            "enabledBy": "paypal-venmo"
          },
          {
            "value": "googlepay",
            "label": "i18n.GooglepayProviderSortingLabel",
            "enabledBy": "googlepay"
          },
          {
            "value": "applepay",
            "label": "i18n.ApplepayProviderSortingLabel",
            "enabledBy": "applepay"
          },
          {
            "value": "amazonpay",
            "label": "i18n.AmazonProviderSortingLabel",
            "enabledBy": "amazonpay"
          }
        ]
      },
      ...
    ]
  }  
}

It should look like:

Info: Adding “heading” for a section can be skipped if it was added before:
schema.json

{
  ...,
  {
    "name": "Payments",
    "settings": [
      ...,
      {
        "type": "heading",
        "content": "i18n.QuickPaymentButtons"
      },
      ...
    ]
  }  
}

Adding wallet buttons to theme markup:
To render wallet buttons next code should be paste under the 'Add to cart' button on the Product details page:

{{#if this.with_wallet_buttons}}
  {{#if wallet_buttons}}
    <div class="your-class-for-wallet-buttons-list">
      {{{wallet_buttons}}}
    </div>
  {{/if}}
{{/if}}

It should look like:

And That's It! The wallet buttons should be always available to the customer except:

Wallet buttons should be hidden if the product details form is invalid.
Wallet buttons should be hidden if the product is not purchasable or out of stock.

If you would like to learn more about the use of Wallet buttons on your Product Detail Page please check out our Configuring Wallet Buttons Documentation. Also look for more to come in 2023 with the use of Wallet Buttons on the Product Detail Page. Including integrations with ApplePay, GooglePay, AmazonPay.

Introducing the Point of Sale Foundation

Stephen Hilliard — Thu, 05 Jan 2023 18:34:25 +0000

“Introducing an open-sourced point-of-sale app to unify the online and in-person payments experience with Stripe Terminal.”

BigCommerce previously announced the release of the Subscription Foundation and now the Point Of Sales Foundation. You may be asking what the Foundations are.

To help you with your ecommerce journey, BigCommerce is now offering a faster, more flexible path to custom commerce solutions for enterprises. The BigCommerce Foundations are open-sourced apps that provide a base for enterprise merchants to create highly customized customer experiences with less upfront development work. 70% built by BigCommerce, merchants can customize 30% on top of our foundations with the help of developers and third-party agencies. This foundation means you get access to a base layer of open-source technology that’s easy to build on, so you can acquire the right capabilities faster.

What is the POS Foundation?

**
In a nutshell, Point of Sale Foundations unifies your online and physical stores. By using Stripe Terminal as a point of sale solution you can connect your on-site and online business using Stripe’s POS hardware. Once connected, you can use the POS terminal to select products from your online store and accept in-person payments. This setup is great for ecommerce merchants who need to accept in-person payments.

POS Foundations accelerates your Stripe Terminal implementation by removing hundreds of hours of upfront work and offers a head start on building a customized POS solution that uses secure, pre-certified EMV card readers. Merchants can unify their online and offline channels and create experiences tailored to a variety of retail use cases and business models. With the POS Foundations, you also benefit from automatic reconciliation, cloud-based fleet management, and a single view of their customers and products.

What the POS Foundation Provides:

Merchant and employee onboarding experience
POS Front-end
PIN-entry login
Category, product, and option selection
Customer lookup and selection
Connected terminals selection
Integration to BigCommerce customer groups and promotions management (including automatic, customer group, order-based, and product-based discounts)
Integration into APIs and webhooks **

What the POS Foundation Gives You:

A faster path to POS customization
Enable your omnichannel vision by bringing your in-store experience together with ecommerce and other key channels
Less upfront development work so you can spend time on building standout in-store experiences
Expansive possibilities beyond the limits of off-the-shelf POS solutions

Foundations takes Stripe Terminal to the next level by removing hundreds of hours of upfront development work. The POS Foundation is a manual connector app that uses a store API account. Customize your in-person payment experience with an open source point-of-sale application. Easily set up, manage, and use pre-certified Stripe card readers that ensure secure transactions to unify your online and offline channels for all kinds of retail use cases and business models. BPOS WisePOS E card readers are industry-certified and end-to-end encrypted to manage payment card data. Order readers from the Stripe Dashboard and have them shipped to a location of your choice.

While currently only available in the U.S., Canada, United Kingdom, Ireland, France, Germany, and the Netherlands. We are looking to expand this foundation and would like to collaborate with interested agencies. If you would like to submit a PR for contribution, you can do so here. We also invite you to join other developers working with POS Foundations and the BigCommerce platform in our BigCommerceDevs Community space on Slack; if interested apply here.

Introducing the Subscription Foundation

Stephen Hilliard — Thu, 05 Jan 2023 18:27:05 +0000

BigCommerce & Stripe are bringing the Subscription Foundation for Store Owners and Developers convenience…

The Subscription Foundation is the latest open-source application out of the BigCommerce Foundations tool set that “helps you accelerate custom development of specific use cases by leapfrogging the foundational integration points.” The Subscription Foundation is a “subscribe and save” application framework that provides a template to scaffold custom subscription billing and invoicing solutions for your business or client. This framework will fast track builds of custom subscription experiences on the BigCommerce platform, potentially saving you hundreds of hours of development time with a user experience that fits nicely within the BigCommerce control panel.

This suite of open source apps provides enhanced functionality, which connects seamlessly with your store and Stripe account. With the resources included in Foundations, you can build customized subscription plans for your products and take advantage of Stripe’s POS terminals to unify your online and physical stores and connect multiple terminals at a single location.

How is this Done?

**
You can build customized subscription plans using the default integration with Stripe Billing, including authentication, merchant onboarding, subscription product management, subscription creation, and customer-facing subscription management, which can significantly help accelerate your development time. Subscription Foundation will utilize the Channels toolkit, and your custom subscription channel will appear in the Channel Manager view of a store’s control panel, alongside your other sales channels.

Subscription Foundation uses Stripe Connect so that your app can use one single connection to submit payments to the previously configured Stripe accounts of multiple BigCommerce merchants. The integration with Stripe and BigCommerce requires that the app uses two keys to issue charges: (1) the merchant-specific Stripe account’s public key and (2) the app-specific Stripe account’s secret key.

The reason two keys are needed is that for development, you will work with the two aforementioned Stripe accounts; the merchant account, which simulates a pre-existing account, and the App Account which you configure as the app’s dedicated Stripe Connect-enabled account. The two accounts will create the following benefits for the merchant:

The merchant can change the Stripe accounts they use without breaking the integration.
The merchant’s Stripe account stores all the entire shopper payment history, including subscription and one-time purchases.

Utilizing this type of approach, the Subscription Foundation creates Multi-tenant functionality. During installation, the app UI prompts the merchant to enter the keys for their store’s Stripe account so that the app can initiate an OAuth authorization code grant flow to link the merchant’s Stripe account to the app’s Stripe Connect-enabled account.

What this means

Build your ideal customer experience, and stand out from competition using Foundations to customize core commerce elements.
Win enterprise merchants by offering unique commerce solutions that natively work with BigCommerce and differentiate your services.
Get a head start on building your own subscription and POS apps with open sourced apps that eliminate some slower parts of the development process.

When you use Foundations, you’re not limited to the capabilities in off-the-shelf products that may not be up to meeting complex needs. With Stripe, we make it easier for you to build customized, globally scalable solutions for your specific needs without starting from scratch, so you can create your ideal customer experience while saving hundreds of hours in development work.

What’s next?

**
If you want to learn more about how Foundations, powered by BigCommerce and Stripe support your business and customers visit https://www.bigcommerce.com/foundations/ to learn more about Foundations for Stripe Billing and Foundations for Stripe Terminal. With Foundations start turning your biggest ideas into reality, and be sure to check back often for the latest updates.

BigCommerce Storefronts Now Support Preload/Early Hints

Stephen Hilliard — Thu, 05 Jan 2023 16:58:01 +0000

BigCommerce Storefronts now support Preload/Early Hints features with Chrome’s addition of supporting HTTP Early Hints.

When you open a web page, the browser requests the HTML document from a server, parses its contents, and submits separate requests for any referenced resources. Developers already know about all the resources a web page needs and which of them are the most important. With that knowledge the developer can request the critical resources ahead of time and speed up the loading process by adding a tag with rel=”preload” to the head of your HTML document: The browser caches preloaded resources so they are available immediately when needed in subsequent requests.

This allows a browser to start downloading critical assets (like CSS/JS files, images, fonts, etc.) very early in the request lifecycle. Which can result in a material improvement in load times for shoppers on stencil storefronts, as they do not have to wait to receive the HTML of the page in order to download large assets. This can significantly improve first paint by pre-populating the browser cache with these assets, and can reduce the impact of a slow response time.

How preloading works:

**
Preloading is best suited for resources typically discovered late by the browser. By preloading a certain resource, you are telling the browser that you would like to fetch it sooner than the browser would otherwise discover it because you are certain that it is important for the current page. For example, font is defined in the stylesheet with a @font-face rule. The browser loads the font file only after it has finished downloading and parsing the stylesheet. Preloading these resources ensures they are fetched before the CSS files have downloaded.

The critical request chain represents the order of resources that are prioritized and fetched by the browser. Lighthouse identifies assets that are on the third level of this chain as late-discovered. A word of caution: unused preloads trigger a Console warning in Chrome, approximately 3 seconds after the load event, that’s why it’s important to use preload sparingly and only preload the most critical resources. Preloading is a powerful performance optimization that has an effect on loading speed. Such optimizations can lead to changes in your site’s Core Web Vitals, and it’s important to be aware of them.

What this means for you:

Provide theme developers with tools to mark critical theme assets for preloading and the ability to nominate high-priority resources.
Automatically preload critical assets, such as Script Manager scripts, payment provider JS, analytics JS.
FCP reduction for first page load.
Faster storefronts with better conversions as a business benefit creating happier merchants with better growth adjustments. If you want to read more you can check out our documentation here: Early Hints & handlebars helpers reference early hints and cdn

Happy New Year from BC's DevRel team!

Heather Barr — Tue, 03 Jan 2023 21:39:14 +0000

Hey devs & Happy New Year 🥳

This Community has grown so much over the past year!
We wanted to take a moment to celebrate you all and how far we've come. We couldn't have done any of this with out all of you, so cheers to the new year -- we're so glad you're with us. 💙

We've been calling 2022 a "Year of Firsts" for the Developer Community and for DevRel here at BigCommerce. We're not done though, in fact -- we think 2023 will have many 'firsts' of it's own. Not only did we see a huge increase in new members for the BigCommerceDevs Slack in 2022, but we also gained a few team members on the BigCommerce DevRel team. These are people you've seen around the Community writing blogs, engaging with you all in Slack and Twitter, joining you in events and even throwing some events of our own!

This recap of 2022 will cover the growth we've seen on Slack, the events we've been involved with, and some other opportunities we've had over this past year.

BigCommerce Developer Community Spaces

Over the past few years our Slack instance, BigCommerceDevs, has taken off 🚀

Year over year, we've seen this space become the best option for peer-to-peer connection and support. It's extremely valuable to not only you, developers, but also for us here at BC!

Full transparency here --> Looking at Slack from January of 2022 to January of 2023, we can see that we've had a ton of new members, in fact over 400, and an increase in active members as well.

Report with BC-ers

👀 Wow, check out Matt Coy up there 🏆

We've also seen our Twitter handle, @BigCommerceDevs, completely transform into a lively and engaging space thanks to @katiehoesley, our Sr. Developer Advocate! 👏

Events

Last year we saw a vast variety of events in the Community! In case you missed any of them, I'll share some details below.

We held our first-ever Unconference back in May, the Events Unconference, to talk to you all about what types of Developer events you'd be interested in for the future. Our team received so much value from this, and even started the internal discussion of a Hackathon (which you'll see later on 😉). This was a lot of fun, thanks to everyone who joined and contributed!

We hosted 2 AMAs in our Developer Slack with a handful of BC-ers on topics from App Development to Page Builder. Were you able to make either of these? If so, what'd you think? What topics would you like to see in the future? Let us know!

Another first was BigComDevX by Space48, which gathered developers from all over to share tips on BC development and general best practices from BigCommerce partners! Shout out to the Space48 team for organizing and hosting the first ever Community-Led event at BC & we can't wait for the next one in 2023!

Twitter Spaces are next on the list. And yes, you guessed it -- they're another first for the Community. 💥 Katie Hoesley has been killing it with these recurring Twitter Spaces, where she meets with members and BC-ers to talk about all-things-tech and BigCommerce.

Last but not least, BigHackathon: Summer '22!
This was an incredible event in the Developer Community. We had teams from all over the world participate in this Hackathon, which indeed -- was the first Hackathon at BigCommerce! Every team had a creative and beautiful app that enhanced the platform in some way. Our team, DevRel, also learned a lot from this event -- what went well, what could have gone better, and what we'd like to try for future hackathons. Thanks to everyone who hacked with us and we look forward to the next!

Betas

This is something not all of you may know, but 2022 was the first year that we hosted beta groups in the Developer Slack.
We had 2 beta groups launch in the second half of 2022 and are still going strong.

This is a great sign for our Community. Other teams internally are aware of how valuable our Developer Slack is to you all and are trying to make beta experiences better by meeting participants where they are. To compliment that statement, the other side is that beta groups in Slack also attract other developers and technical partners to the space that were previously unaware of it.

Other Opportunities

With beta groups being hosted in our Slack instance, more BC-ers engage and/or lurk there as well. Which is really good for the Community and is the direction we want to go, moving forward.

If you haven't yet engaged with someone from BigCommerce in Slack, other than myself, there's a chance that may be changing in 2023. As you can see in the screenshots above, we had a decent amount of BC-ers join BigCommerceDevs, the Developer Slack instance, and a handful of these members jump in threads from time to time. This past year, many BC-ers lurked in Slack to learn about what you're all running into with our platform.

There is a huge opportunity here, in my opinion, which 2022 made light of! If you agree, let us know in the comments below or shoot me a DM to tell me about it!

What's next??

2023 holds the potential for our team to do more for the Community than ever before. That may be a big statement to make, but I really feel that it's true. Our team has recently been put in a great position at the company and we're going to start brainstorming soon. I will share that we do have solid plans in 2023 around community gathering/events and developer resources. If you have any great ideas or requests for us, share below!

Not only is the potential high for our team, but as we grow and attract different types of people to our spaces, the Community becomes more diverse. Which opens up a ton of potential for you all, as well! Different types of people coming together is what Community is all about and having varying perspectives is what takes them to the next level.

Even though the year has just stated, we've already heard interest from some of you in running your own type of Community-Led event this year, both IRL and virtually. This is really exciting to hear and we hope to see it happen! If you're intersted in hosting your own type of event, reach out to us so we can talk about your idea and help out where we can.

We're stoked to see what we accomplish together!

💙 Cheers from the DevRel team @ BigCommerce

Interview with BigCommerce’s Developer Community Manager Heather Barr: A Twitter Space Recap

katie hoesley — Wed, 07 Dec 2022 02:25:13 +0000

Last week, I sat down with our Developer Community Manager, Heather Barr, to chat about our Developer Community on our weekly(ish) Twitter Space.

As you read our interview, you’ll notice how palpable Heather’s passion for this community is. She has (often single-handedly) fostered the growth of our Developer Community throughout her career with BigCommerce, and her answers sound like she has no plans to take her foot off the gas anytime soon. Read on to learn more about the community we’re so lucky to have, and Heather’s vision for the future.

This article is the TL;DR of our Twitter Space!

The Interview

Katie Hoesley: Hey Heather! Thanks for sitting down with me today. Let’s get right into it: can you tell me about what a Developer Community Manager does?

Heather Barr: Thanks for having me! What a loaded question! My primary role at BigCommerce is to advocate for the community’s needs and resources while being a resource to the members as well.

To dive into these — Advocating for the community’s needs! This looks like answering these questions:

What does the community need to thrive?
What can I do to address these needs?

At the moment, this is broken down into two main categories.

Better tooling! The most important tool is our spaces, like Slack. Next are things like improving our swag offering for contributor programs (that we want to revamp!) and events/challenges, optimizing and tracking developer experience, improving onboarding, and supporting opportunities for members to do more with the community (such as working more with us or organizing community-led events and programs), access to additional resources for self-help and discovery within the community or documentation, and lastly — visibility into what’s going on and how to get involved.
More resources! For example, knowledgeable BC-ers who have a similar experience, or more experience, than myself! Since I am the most consistent and present BigCommerce contact in this space (aside from Twitter — you are rocking Twitter!) bandwidth gets pretty stretched. A large effort of mine has been to change this, and not just for the time that I’m here, but beyond that, as well.

This leads me to another large responsibility of my role: being a resource to the members. This looks like acting as someone who can test and share visibility on issues or odd behaviors that our community members are having for a faster turnaround. This benefits our community members and BigCommerce by helping identify bugs and any necessary documentation updates.

Over my tenure here at BigCommerce, my role has gradually shifted focus to these two key aspects. As most of you have likely observed, I have days where I’m more focused on long-term processes and experience improvements (that’s when y’all don’t see me as much), and then I have days where I’m much more active in the community myself. Balancing is tough sometimes, but I do the best I can and am grateful for our members who are incredibly helpful with one another.

KH: Why do developer communities matter?

HB: I can’t speak for all developer communities out there, as they all have different benefits and ecosystems that are being supported — But for companies like ours, they’re so important for a partnership. Not only that but also for building on and improving the platform, together. BigCommerce wouldn’t be the same without our partnerships and without all of the developers out there who are challenging our platform limits and building real solutions to problems our merchants face and even bringing more merchants to BigCommerce through their relationships as agencies. In my opinion, I feel that developer communities are a huge part of DevX, which is an important investment for any company to commit to, especially those that depend on developers.

KH: What is the state of our community/where do we want to go?

HB: Great question, Katie! So, it’s two-sided. I’ll tl;dr it by saying the current state of our community is what I’ll call a layup for BigCommerce and a great peer-to-peer resource for devs. Currently, our members are mostly engaged in peer-to-peer, meaning dev-to-dev, conversations, and sometimes engaging with BigCommerce employees as well.

As far as where we want to go — This is what I meant by a layup for BigCommerce’ — This is the perfect time for BC-ers to step in and learn about developers building on and for our platform. Katie, Stephen (our Developer Advocates), and I still have work to do on this front to foster that connection, but it’s something I’ve personally spent a lot of time on recently, and may have some news soon.

I want to leave this question with a note — We’re extremely lucky to have so many of you who are open to helping and sharing your experiences. Specifically speaking about our Developer Slack space — this is the general vibe of the community, at the moment, and I hope this remains a constant as we grow!

KH: Any cool community things coming up?

HB: Cool things? Yes! Over the next few months, there are a handful of things I’m excited about.

To start with — DevWeek! DevWeek is an internal collaboration week that I played a big part in organizing for some of us internal folks at BigCommerce. This is a week where our developers, our DevDocs team, the DevRel team, and I are coming together to talk about areas of our roles that overlap and to work together in solving some common problems that you all face. We’re also going to be using this time to plan for 2023, so I will probably have more to share about fun opportunities closer to EOY!

I love that these Twitter spaces are a constant opportunity for our teams and our members. Every week this is something that excites me. Katie, you do a great job with these, and a note to all of you who are here or will be listening to the recording: if there’s a topic you want to hear about, let Katie know! Or if you want to get involved to be a guest, let her know! I would love to see more devs and partners co-host or be guests on these, as this continues to grow.

Our customer community manager, Jacinda Espinosa, will be running another series of Partner Q&A’s in Q1. This is where partners can, for example, run a demo of their app and host a Q&A immediately after in our primary merchant-facing Facebook community group to get feedback, ideas, questions, etc! If you’re interested in joining, apply here!

KH: What kinds of community contributions do we want?

HB: We’d love to see our members contribute by creating content! Written or visual tutorials, blogs, how-to content, general talks, videos, or blogs on your development process, maybe something interesting your app solves or an interesting solution you created for a problem other developers likely encounter as well. Anything unique is amazing to see!

To mention a few who’ve done things like this:

Tom Robertshaw from Space48 does a great job at this with the Space48Apps YouTube channel.
Although this was last year, Max Karlsson had a memorable contribution I’d like to talk about. He wrote a 2 part blog on implementing the forgotten password workflow for headless, as it was a common topic in the community at the time — that was incredible to see and I won’t ever forget that. (Check out Part 1 and Part 2 of that blog!)
Just the other day, Jack Harner wrote a blog on Stencil CI-CD via GitHub actions. Check it out if you haven’t seen it yet!
During BigCommerceDX, the most recent community-led event organized by Space48, Matt Coy from ArcticLeaf demonstrated an Advanced Handlebars live-code tutorial that was so popular and valuable in the community.

These are just some examples, but the main takeaway is that the most impactful contributions are those that help your fellow community members. Engaging in our community spaces with each other, on Slack for example — is incredibly valuable and my absolute favorite type of contribution.

KH: What are some pie-in-the-sky goals you have for the community over the next few years?

HB: My main goal with the Dev Community over the next few years is for it to become more of a collaborative space between BC-ers and the members. Last year, I created and ran a pilot program focused on a couple of BC-ers for exactly that purpose — and learned a lot from it. Notes were taken, adjustments were made and I’m about to try again in a much bigger way.

I believe this goal has the best chance of making the Developer Community not just a space for developers, but a space that is used as a part of BigCommerce’s development lifecycle. I can’t wait to show our Community members what I’ve been working on for them!

KH: What would you like to see more of from/in the community?

HB: I would like to see more collaboration in our community between BC-ers and external developers, and I know I’m not alone in that!

I think we’re at a great time with the right people on board to start seeing these changes. Now that our DevRel team is ramped up and settling into their roles, we’re able to approach problems from different sides to move forward faster, together.

Secondly, I hope to see more community-led events, either virtual or IRL events and gatherings that our members organize and host themselves. I think as the community grows, more individuals would be interested in something like Space48’s virtual BigCommerceDX last year and other types of events where they can meet each other and share the awesome things they build on the platform.

I hope to create new ways to reward our members who do this and incentivize others to get involved!

KH: You’ve mentioned “D2D”. What’s this new program you’re talking about?

HB: I can’t say much more about this program just yet! I’ve been hearing feedback from the community and I’ve been working for y’all in the background. It’s my mission to deliver more value in our spaces to help you get unstuck faster, and have more opportunities to connect with internal BigCommerce folks and others in the community in creative and productive ways.

KH: What’s the best part about managing the BigCommerce Developer Community?

HB: Goodness, there isn’t just one!

Seeing how helpful and involved the members are taking the cake. I also really do feel like I’m making an impact here, on both the inside and outside. I know that I’m not always available or able to answer some of the questions that are asked by devs and partners, but the work I’ve been doing to help address this in the shadows I feel will start to pay off soon.

Next to that — finding and working with so many like-minded people at BigCommerce has been awesome. Branching out and creating new relationships with other BC-ers is something that has taken some time in my role, as I didn’t seek this out much when I first started. As I’ve grown in my role and met people like you, Katie, who reminded me of the power relationships have in the workplace and finding more advocates for our community members from teams outside of our own, has become one of my favorite parts of my role.

Have more questions?

We love hearing from our community members! If you have questions, comments, or anything in between, please reach out to us! You can reach both Heather and me in our Developer Slack space (if you’re a developer and aren’t in our Slack space, let’s change that! Follow this link to apply!), you can comment on this article, tweet at @BigCommerceDevs or @Katie_Hoesley, or email devrel@bigcommerce.com.

BOPIS (Buy Online Pickup In Store) APIs now Available in Open Beta

katie hoesley — Mon, 05 Dec 2022 16:25:57 +0000

BOPIS is available!

An exciting new feature of our multi-location inventory functionality is here! Buy online pick up in store (BOPIS — check out the documentation here!), also known as Click & Collect outside the United States, is now available in open beta via our APIs. This update enables merchant developers, tech partners, and agencies to create custom experiences around picking up items at their retail locations.

What exactly is an open beta?

BigCommerce open betas include production use ready functionality, which is subject to change based on the feedback from beta participants. Open betas are a great way to try out the latest functionality and have your voice heard by giving feedback to the BigCommerce team. Participants opt in to open betas, and everyone is eligible!

What’s included in the release?

We’ve released 2 new APIs, including the Pickup Methods API and Inventory API, and updated a handful of existing APIs. Together, this means that merchants who have multiple retail locations will have the tools to create custom BOPIS/Click & Collect experiences that are tailored to their buyers’ preferences.

I’m interested! What are my next steps?

To opt in, locate and click on Settings in the Control Panel menu, located on the left-hand side. Once you’ve done so, select Inventory in your BigCommerce Control Panel, as seen below.

After selecting “Settings”, select “Inventory”

A banner with an option to Try it now should be on the top of the page_._ If you want to enable the BOPIS APIs, select that! This banner also provides you with more information about the BOPIS APIs, what is coming soon, and a link to relevant documentation (also found here).

BOPIS APIs opt-in banner

To enable BOPIS APIs, click Try it now! Once you click that, you’ll see the banner pictured below outlining what is available in the beta as well as providing supplemental documentation about the API at the top of your screen.

BOPIS APIs early access mode trial success

And that’s it! You now have BOPIS enabled on your store. To learn more about our APIs, please check out ourBOPIS APIs documentation.

If you still have questions, comment on this article ortweet at us!

Staging by StagingPro Now Available on BigCommerce

katie hoesley — Mon, 05 Dec 2022 16:23:40 +0000

At BigCommerce, we understand the importance of merchants being able to preview changes to a store before pushing those changes to production. Nobody wants users having a confusing, subpar experience because they encountered some non-production-ready content!

How can we help make sure that never happens? BigCommerce now features staging by StagingPro!

StagingPro is a comprehensive enterprise integration for staging. Seamlessly integrate staging environments with existing workflows and tools, all from within your BigCommerce control panel.

“We are thrilled to partner with BigCommerce to transform the way merchants and agencies design, develop and deploy BigCommerce stores. StagingPro is built to eliminate the day-to-day challenges retailers and agencies face in this fast-evolving technology space.

Susant Patro, CEO of StagingPro

Now, instead of using a secondary store for staging and testing purposes, BigCommerce merchants are able to use StagingPro to stage and test on their primary storefront. This is a particularly huge upgrade for anyone who works in our ecosystem and enjoys experimenting with design and user experience flows before pushing to live production.

Why is staging important?

Staging is important for many reasons, but one reason really stands out: you want to test and observe your changes and approve them before pushing them to production where users interact with your program. It’s important for users to have intuitive, friction-free experiences online, and programs that haven’t been adequately tested are frequently problematic.

Staging allows developers, and in this case any merchant or developer on the platform, to observe and interact with their changes before making them visible to users. This allows for optimal user experiences, repeat customers, the list goes on!

“We are setting a new era of digital experiences through moving data, design, code, generating previews and scheduling deployments across multiple BigCommerce stores. StagingPro will accelerate RoI, improve efficiency and reduce the total cost of ownership for businesses worldwide.”

Susant Patro, CEO of StagingPro

StagingPro is a cost-effective, highly automated staging solution that allows for web development at the speed your business demands. StagingPro allows you to build staging websites as exact replicas, including the same data as the production environment, even including theme!

The best part?

You’re able to easily manage your StagingPro environment launches all from your BigCommerce control panel.

I’m interested! What’s next?

If you think Staging by StagingPro is for you, request a demo!

If you have questions, comment on this article ortweet at us, or send an email to Hello@stagingpro.com!

BigCommerce + ethos: A Partnership Exemplifying the Links Between Web3 & Ecommerce

katie hoesley — Fri, 18 Nov 2022 15:11:33 +0000

BigCommerce <> ethos

Have you been waiting for the option to have a branded NFT experience that lives directly in your store? Are you a fan of digital assets but want to be sure they have real value for your customers? Do you want users of all technical skill levels to be able to interact with these digital assets?

Good news!

Any merchant with a store on the BigCommerce platform now has the option to work with ethos! ethos is a white label NFT platform that enables brands to sell or issue NFTs.

“ethos’ platform allows brands to offer NFTs through a fully branded experience that includes real-world utility. Added utility such as discounts, air drops, early access, or special products when holding an NFT makes ethos the chosen partner for brands who want to reward and grow their customer base.” (ethos Named BigCommerce Technology Partner Press Release)

How does it work?

It starts with ethos, who creates a fully branded experience for merchants by capturing their brand’s assets, creating landing pages where users can pre-register for an NFT drop or go through the purchasing process, and more!

ethos’ NFTs can be equipped with real-world value like discounts, air drops, early access, or special products when holding an NFT. Whether your customers are crypto pros or want to use a credit card to purchase items in your store, ethos provides barrier free transaction options. Customers can buy these NFTs with cryptocurrency or traditional payment methods, and don’t need to set up their own crypto wallets and keys if they would prefer not to.

Imagine a merchant launches their first NFT and adds to that NFT a perpetual 20% off all purchases coupon that now lives in the customer’s account. Customers don’t need to track down any email confirmations or gift cards, it’s just right there in their customer account, and 20% discounts are applied to their orders!

These NFT holders are now a segment of your audience you know a lot about, and you have a direct line of communication with them: their NFTs. You can now send out special offers, freebies, event invitations, etc. to certain segments based on NFTs they’ve purchased from you.

ethos also has what’s called an eDrop. An eDrop gives you the ability to issue free NFTs to anybody! This allows merchants to issue NFTs to anyone and have any utility attached to them — maybe they send them to their friends and family to give them a 20% discount on product, maybe they want to surprise a loyal customer with a one-time freebie — whatever!

Non-crypto experts make up the mass majority of consumers today, so catering to customers with diverse crypto knowledge levels is paramount to achieve mass adoption of Web3 concepts like NFTs. ethos’ ease of use makes it possible for any merchant to hop aboard the NFT train.

I’m interested! What’s next?

If you want to check out what this looks like in practice, Saddleback Leather will be the first BigCommerce merchant to launch using this innovative platform at the end of November.

Saddleback Leather’s ethos landing page

You can go totheir ethos landing page, pictured above, and either sign up for the next collection drop or, once the collection is available, you can buy your NFT directly on that page. The NFT(s) you buy will actually live directly in your user account on the Saddleback Leather store.

If you are a BigCommerce merchant and are interested in applying for the early adopter program, or to learn more about NFTs, please click here!

BigCWeb3

Getting Started: Use Building Blocks to Compose Your Headless BigCommerce Storefront using Next.js,

katie hoesley — Wed, 16 Nov 2022 17:54:51 +0000

Getting Started: Use Building Blocks to Compose Your Headless BigCommerce Storefront using Next.js, Contentstack & Netlify!

Last week the Jamstack Conference happened in San Francisco, and BigCommerce’s team was excited to attend and present one of our starter repos!

As a composable commerce engine, we facilitate developers leveraging modern technologies and approaches like Jamstack. Open SaaS gives merchants much more flexibility and freedom of choice while still maintaining the benefits of using a SaaS platform. It’s important to us that developers get to use the tools they want to use, which is why we enable them to build storefronts with whatever their preferred tech stack is.

BigCommerce’s flexibility allows merchants to use our APIs to integrate to their existing systems and easily install third-party applications without complicating the management and upkeep of their BigCommerce store. With our headless approach, you can build with your preferred meta framework and deploy your front end anywhere.

What does the starter include?

This proof of concept headless storefront starter repo allows you to fire up a storefront with the following composable tech stack:

Next.js as our frontend framework
Contentstack as our Content Management System
BigCommerce as our Commerce Engine
Netlify to deploy — we want to deploy on Netlify because they allow the level of stack flexibility that our users want to use!

Let’s check out the repo!

1.✅ You’re here! The first step is being in this repo and hitting the “Deploy to Netlify” button at the bottom of this ReadMe.

You need a BigCommerce store! Login or Sign Up to set up a new BigCommerce store to use! Once you’ve logged in or signed up, follow these instructions to obtain your BigCommerce API credentials.
Create an account or login to Contentstack.
Create a “Stack” by selecting “+ New Stack”, title it, add a description, and click “Create”.
Now that your Stack has been created, let’s identify your API keys. Navigate to the “Settings” icon on your left hand panel.

Scroll down and select “Tokens”. This will take you to a page that has a “+ Delivery Tokens” button. Click that, and enter a name and description for your new API keys.

Select the proper branch you’re working from and your production environment (you may need to also create a production environment). Then click “Generate Token”.
If successful, you should see something like this:

Hang on to these variables, you’ll need them in an upcoming step.
Now, back to the ReadMe! Hit the “Deploy to Netlify” button found at the bottom of the page.

Once you’re brought to the page pictured below, select “Connect to Github”

Once you’re brought to this page (seen in screenshots below), give your repository a unique name and enter all of your BigCommerce and Contentstack API credentials.

Save and Deploy!

The deploy process has begun! This may take up to 10 minutes, and will bring you to a page that looks like this:

You can watch your project’s progress by clicking on the tab pictured below:

If you click into that tab, once your build is successfully complete, you’ll see something like this:

To view your site, click “Open Production Deploy” or “Permalink” — both will bring you to your deployed site!

You’re deployed! Great job! 👏

I want to use the starter! What’s next?

Fork and clone the repository here and give it a go, following the steps above (also available in the ReadMe file)! Before you get started, you will need a Contentstack account and a BigCommerce store so you’re able to obtain the necessary API keys.

If you’re building headless storefronts on the BigCommerce platform, be sure to join our Developer Slack space so you can access our #headless channel where you can pose questions and discuss with fellow developers doing similar things!

If this tech stack isn’t exactly what you’re looking for:

Still have comments? Questions? Leave a comment or tweet at us! @BigCommerceDevs or @KatieHoesley.