Buyers always see current products and prices, stay signed in across visits, and are only asked for a card when their payment terms call for one. Companies in Canada and Mexico can now register, and a round of fixes makes browsing and checkout more dependable.
B2B buyers reorder on a schedule, expect their negotiated prices, and leave when a storefront gets in the way. This release is about removing that friction: the information buyers see is always current, a returning buyer picks up where they left off without signing in again, and checkout follows the payment terms you have already agreed with each account. It also opens the storefront to Canadian and Mexican customers and fixes the small failures that erode confidence in a site.
Your buyers always see the latest products and prices. Changes made in Nymble Admin appear on the storefront on the next page load.
- What changed: the storefront no longer holds on to its own copy of catalog data or rendered pages. A price update, a stock change, a product edit, a category you add, rename, or retire, and a replaced product image all show on the very next visit. Product images are now served from Nymble’s own image domain, which is what lets a replaced picture appear immediately rather than after a delay.
- Why it matters: a buyer who sees yesterday’s price, or an image of a product you replaced, calls your team or orders the wrong thing. Your ecommerce team can make a change and trust that the storefront is showing it.
Signed-in buyers always get their own prices. A customer who is signed in never sees the public version of a product page.
- What changed: a signed-in buyer could previously be shown a product page prepared for logged-out visitors, with a “Login To See Pricing” prompt instead of their pricing, or category tiles that were out of date. That no longer happens; every signed-in visit is rendered for that customer.
- Why it matters: account-specific pricing is the point of a B2B storefront. Buyers should never have to wonder whether the price on screen is theirs.
Retired products stay out of the catalog. Products you deactivate in Nymble Admin disappear from browsing, category pages, and the product sitemap sent to search engines.
- Why it matters: buyers do not find, and search engines do not index, items you no longer sell. Fewer questions about unavailable products reach your reps and customer service.
Faster, easier repeat purchasing
Buyers stay signed in between visits. A buyer who signs in on their browser stays signed in for up to 30 days.
- What changed: previously a session ended an hour after sign-in, so a buyer building an order over a morning, or coming back the next day, had to sign in again. Sessions now renew quietly in the background, and each browser holds its own session.
- Why it matters: repeat purchasing is where B2B revenue lives. A buyer who returns to a signed-in storefront with their cart and pricing waiting is far more likely to complete the order.
Signing in returns buyers to what they were doing. Every Login button on the storefront brings the buyer back to the page they were on, including search results and the page number of a listing.
- What changed: the return-to-page behaviour now works from every Login button, checkout’s included, and preserves the search terms and page a buyer had reached. The Login button on the checkout page, which previously did nothing, now signs the buyer in and returns them to checkout. Signing out lands on your storefront instead of the sign-in service’s page.
- Why it matters: a buyer who found the right product on page three of a search and then had to sign in should land back on that product, not on the home page.
New carts follow your order types. A cart started on the storefront takes your organization’s default order type, the same one Nymble Sales uses.
- Why it matters: orders arriving from the storefront and from your reps share the same classification, so operations teams process them the same way without reclassifying.
Buyers can find their account number. My Account now shows the customer number beside the company name.
- Why it matters: when a buyer contacts your team or their rep, they have the identifier your back office already uses on their orders and invoices.
More flexible B2B payments
Ask for a credit card only when the account’s terms call for it. Customers on account terms can place orders billed to their account, while customers whose terms require payment are asked for a card.
- What changed: a new “Require a Credit Card For” setting under Payment Settings lets you keep requiring a card from every customer (the default) or choose the payment terms that require one, selected from your organization’s own list of terms. A buyer on any other term sees payment as optional and their order is billed to their account, unless they choose a saved card or add a new one. A customer with no terms on file is always asked for a card.
- Why it matters: most B2B relationships run on Net 30 or similar terms. Forcing a card at checkout from a customer who has an approved account is friction that pushes orders back to phone and email. This setting lets the storefront honour the terms your credit team has already granted, while keeping card payment mandatory where it should be.
Better international selling
Canadian and Mexican companies can register. The registration form accepts Canadian and Mexican postal codes and labels the field the way those buyers expect.
- What changed: the postal code field only accepted US ZIP codes, so a Canadian address could not complete registration. It now accepts Canadian and Mexican codes, reads “Postal Code” for those countries and “ZIP Code” for the US, is required (the form always said it was), and tidies what was typed so “k1a0b1” is stored as “K1A 0B1”.
- Why it matters: new accounts from across the border register themselves instead of asking your team to set them up, and the addresses arrive consistent enough for shipping and invoicing.
Important fixes and refinements
Products in more than one category link and breadcrumb correctly. A product filed under two categories previously linked to an address that ran both category paths together, with a breadcrumb trail that led nowhere. It now links through the category the buyer is browsing and shows one clean trail, and search engines are given a single address for it.
Deeper category pages open. A subcategory that has subcategories of its own no longer returns “Page Not Found”; category pages open at any depth, and the links on category cards and in the sitemap all resolve.
Pages that showed raw template text render properly. The cart page, search results, a flipbook’s product tags, the header cart icon, View Cart, and Checkout could fail to render and show placeholders like ”{{ item.productName }}” instead of the buyer’s items. All of them render correctly again, and View Cart line-item images load. A brief flash of the cart review dialog during page load is gone as well.
Storefronts installed in a subdirectory link correctly. Registration and category links now respect a WordPress installation that lives below the site root.
A clearer API key setting. The settings field is labelled “Storefront API Key”, explains what a storefront key is for, and confirms the saved key is one.
If your host runs its own page cache, the storefront now marks a signed-in buyer’s requests so that cache skips them. Signed-out storefront pages should still be excluded from host-level caching so buyers see current information.