Search, shipping, and promotions can appear simple to customers while depending on several systems and business rules behind the scenes. When something stops working, the visible symptom is not always where the underlying problem began.
An irrelevant search result may trace back to incomplete product data. A missing shipping option may be caused by package details, a carrier connection, or an account-specific rule. A promotion may be configured correctly on its own but behave unexpectedly when another discount also applies.
The most reliable way to investigate these problems is to trace the information through each layer rather than changing several settings at once.
The checks below are intentionally platform-neutral. Some may be available to an ecommerce administrator, while changes to integrations, search logic, custom code, or carrier connections may require someone familiar with the platform and its dependencies.
1. Buyers Can’t Find the Right Products
Search is especially important in B2B ecommerce, where buyers may work with large catalogs, technical specifications, manufacturer part numbers, customer-defined SKUs, or products available only to certain accounts.
When relevant products do not appear near the top of the results, buyers may refine the query repeatedly, browse manually, contact a representative, or leave without completing the task.
A useful search diagnosis starts with the source information and follows it through indexing, visibility rules, and result ranking.
Confirm that the source data exists
Search can only use information that is available to it. Begin by reviewing the data customers are likely to enter.
Depending on the catalog, that may include:
- Product names
- SKUs
- Manufacturer part numbers
- Customer part numbers
- Descriptions
- Technical specifications
- Product attributes
- Common abbreviations
- Compatibility details
- Manuals and documents
- Replacement-part relationships
A search for a part number cannot succeed if that identifier is missing from the product record. The same is true when buyers use familiar industry terminology that does not appear anywhere in the catalog data.
Review whether important values are complete and consistent across the products customers need to find.
Confirm that the correct records are being indexed
Once the data is available, determine whether it is reaching the search index.
Relevant records may include:
- Products
- Product variants
- Categories
- Articles
- Technical documents
- User manuals
- FAQs
- Replacement parts
Confirm:
- Which records are included
- How often the index is updated
- Whether recent updates completed successfully
- Whether indexing errors were reported
- Whether unpublished or incomplete records are excluded intentionally
- Whether customer-specific products are handled correctly
A product can exist in the ecommerce database while remaining unavailable in search because it was never sent to the index or the index has not been refreshed.
Confirm that the important fields are searchable
A record may be indexed without every useful field being searchable.
For example, a product could be indexed by name and description but not by SKU. That would allow a general product search to work while preventing an experienced buyer from finding the same item by part number.
Review which fields are searchable and how they are treated. Exact identifiers such as SKUs may need different logic than descriptive terms or technical attributes.
For B2B catalogs, consider whether buyers need to search by:
- Internal SKU
- Manufacturer number
- Customer-defined part number
- Model number
- Specification
- Product family
- Compatible equipment
- Application
- Document title
Review product visibility rules
A highly relevant product may still be excluded from the results because the buyer is not eligible to view or purchase it.
Review rules related to:
- Customer accounts
- Contract catalogs
- Markets or regions
- Language
- Publication dates
- Inventory
- Product status
- Account permissions
- Customer-specific assortments
- Discontinued-product handling
These exclusions may be intentional. The goal is not to make every product visible to everyone. It is to confirm that the rules match the intended customer experience.
Review ranking and relevance
If the correct products are present but appear too far down the results, review how the search solution ranks them.
Some search platforms allow teams to assign more importance to fields such as an exact SKU, product name, category, or specification. They may also support:
- Synonyms
- Abbreviations
- Spelling variations
- Fuzzy matching
- Result merchandising
- Customer-specific relevance
- Behavioral ranking
- Product availability rules
An exact SKU match may deserve the top position, while a broader descriptive search may rely on product names, specifications, and category context.
More expensive search technology is not automatically better. Some platforms provide greater control over relevance, synonyms, analytics, and merchandising, but the value depends on the limitations of the current experience and the way customers search.
Review actual buyer behavior
Search analytics can help the team distinguish an isolated issue from a recurring source of friction.
Review:
- Most-used search terms
- Zero-result searches
- Queries that are repeatedly refined
- Results that receive clicks
- Search sessions that lead to a quote, cart, or order
- Terms that lead customers to contact sales or service
- Differences among customer or account types
Improving search may create meaningful value when buyers depend on it to find products. Establish a baseline so the team can determine whether a change improves product discovery, task completion, or another relevant outcome.
Reduce the chance of future search problems
Helpful controls may include:
- Required product fields
- Reports for missing identifiers and attributes
- Alerts for failed indexing jobs
- Automated checks for products missing from the index
- A maintained synonym list
- Regular review of zero-result terms
- Tests for customer-specific visibility
- Relevance reviews for common queries
- Post-release search checks
2. Shipping Rates Are Missing or Inaccurate
B2B shipping can involve more than choosing between standard and expedited parcel service. Orders may ship from several warehouses, require freight or special handling, use negotiated carrier accounts, or follow rules specific to the customer.
When a shipping rate is missing or incorrect, the issue may come from the shipment data, store configuration, carrier connection, custom logic, or carrier service itself.
Start by identifying whether a rate request was sent, what information it contained, and what response came back.
Review the shipment inputs
A carrier needs enough information to determine which services are available and what they cost.
Confirm the accuracy of:
- Origin address
- Destination address
- Postal code
- Country and region
- Residential or commercial designation
- Package weight
- Package dimensions
- Number of packages
- Shipping classification
- Declared value
- Special-handling requirements
- Hazardous or oversized-product indicators
- Units of measure
The origin should generally reflect the location fulfilling the shipment, not necessarily the company’s headquarters. This becomes especially important when the business uses several warehouses, dropshipping, or a third-party logistics provider.
Review the store’s shipping configuration
A carrier may return valid services that the ecommerce platform later excludes.
Review:
- Enabled carriers
- Enabled service levels
- Market and country restrictions
- Customer-specific shipping methods
- Minimum or maximum order rules
- Warehouse assignments
- Product-level exclusions
- Free-shipping rules
- Handling fees
- Store-pickup eligibility
- Freight requirements
A shipping option may be unavailable because it does not meet a business rule rather than because the carrier failed to return it.
Review carrier authorization
Carrier integrations require a valid account and current authorization. The exact method depends on the carrier and integration being used.
Confirm:
- The carrier account is active
- Application credentials are correct
- Required authorization tokens are valid
- The integration uses the carrier’s current authentication requirements
- The correct account number is being used
- Negotiated-rate access is configured appropriately
- The test and production environments have not been confused
Avoid sharing sensitive credentials in ordinary support messages or logs. Someone familiar with the integration should verify them through the approved configuration process.
Review communication with the carrier
Determine whether the platform can reach the carrier endpoint and receive a response.
Possible causes include:
- Network restrictions
- Firewall or proxy settings
- Certificate issues
- Carrier API outages
- Timeouts
- Rate limits
- An outdated integration
- A malformed request
- Custom-code errors
Hosted environments can still experience network, security, or provider-related problems. The platform vendor or hosting provider may need to help confirm whether the request is leaving the application and whether a response is returning.
Review the carrier’s response
A successful connection does not guarantee that a usable rate will be returned. The carrier may reject the request or exclude services because of the shipment details.
Review the response for:
- Address errors
- Unsupported routes
- Missing package details
- Service restrictions
- Account problems
- Invalid units
- Oversized or restricted products
- No eligible service for the shipment
- Warnings that the ecommerce platform may be ignoring
Preserve the relevant request and response information without exposing credentials or sensitive customer data. This helps the technical team see whether the carrier rejected the shipment or the ecommerce platform mishandled the result.
Review post-response filtering
After rates are returned, the platform may apply additional rules before showing them to the customer.
That logic may:
- Remove services that are not enabled
- Apply account-specific methods
- Add handling fees
- Hide rates for particular products
- Select rates by warehouse
- Replace parcel options with freight
- Suppress options outside an expected delivery window
- Rename carrier services
If a rate appears in the carrier response but not at checkout, this filtering layer is an important place to investigate.
Plan the customer experience when rates are unavailable
The business should decide what happens when a dependable rate cannot be calculated. Depending on the order and business model, the site might:
- Display a clear error and ask the customer to review the address
- Offer an approved fallback method
- Allow the order to be submitted for freight confirmation
- Route the customer to a quote request
- Ask the customer to contact the team
- Use a documented estimated rate
Avoid silently assigning a zero-dollar rate unless free shipping is genuinely intended. The message should explain what the customer can do next without exposing unnecessary technical details.
Reduce the chance of future shipping problems
Helpful controls may include:
- Monitoring carrier errors
- Alerts when checkout returns no rates
- Credential and token-expiration monitoring
- Tests for representative destinations
- Tests for common package types
- Checks for parcel, freight, pickup, and special-handling scenarios
- Post-release shipping tests
- Documented fallback behavior
- Clear ownership of carrier accounts and integrations
3. Promotions Behave Unexpectedly
Promotions become more complex when several discounts, customer groups, pricing agreements, products, markets, and shipping rules interact.
This is especially important in B2B ecommerce, where contract pricing, volume discounts, distributor agreements, and account-specific terms may need to take precedence over public campaigns.
The first step is to document the intended business rule before changing the platform configuration.
Clarify promotion eligibility
For each promotion, define:
- Which customers are eligible
- Which accounts or groups are excluded
- Which products and categories are included
- Which products are excluded
- Whether contract-priced products qualify
- Whether quotes qualify
- Which markets and currencies apply
- The start and end dates
- The relevant time zone
- Minimum order or quantity requirements
- Usage limits
A promotion that appears broken may be following an eligibility rule that was not communicated clearly or configured consistently.
Define priority and stacking rules
Do not assume that the highest discount should always win. The intended priority depends on margins, customer contracts, campaign goals, and the promises made to the buyer.
Document:
- Which promotions may combine
- Which promotions are mutually exclusive
- Whether contract pricing takes priority
- Whether coupons can combine with automatic discounts
- Which rule should be evaluated first
- What happens when two promotions have the same priority
- Whether the customer receives the best eligible offer or a predetermined offer
The configured logic should reflect the business decision—not simply the order in which rules happened to be created.
Use promotion codes deliberately
Promotion codes can be useful when the campaign is designed around a code. They should not be added merely as a backup for an automatic promotion that is configured incorrectly.
Creating a second discount path may introduce unintended stacking, inconsistent customer experiences, or additional support questions.
When a code is part of the campaign, test:
- Valid and invalid codes
- Eligible and ineligible customers
- Included and excluded products
- Usage limits
- Start and end dates
- Interactions with automatic promotions
- How the error message appears
Define how free-shipping thresholds are calculated
Businesses differ in whether a free-shipping threshold applies before or after discounts. Neither approach is universally correct.
The important questions are:
- What policy does the business intend?
- What calculation does the platform use?
- What does the customer-facing message promise?
For example, a site advertising “Free shipping on orders of $500 or more after discounts” should evaluate the discounted merchandise total. A site using a pre-discount threshold should say so clearly when the distinction matters.
If the platform cannot support the intended rule through configuration, custom logic may be required. That change should be tested against taxes, shipping methods, other promotions, returns, partial refunds, and platform upgrades before release.
Test realistic promotion combinations
A promotion may work correctly by itself and fail when another rule also applies. Build a test matrix before activation.
Include scenarios such as:
- Eligible and ineligible customers
- Contract-priced accounts
- Included and excluded products
- Orders immediately below and above a threshold
- One automatic promotion
- Several automatic promotions
- A promotion code with an automatic discount
- Free shipping before discounts
- Free shipping after discounts
- Volume discounts
- Start and end dates
- Different time zones
- Multiple markets or currencies
- Returns and partial refunds
For each scenario, document the expected result and compare it with the platform’s calculation.
Review the complete order calculation
Promotions can affect more than the product subtotal. Depending on the configuration, they may interact with:
- Customer-specific pricing
- Tax
- Shipping
- Handling charges
- Payment fees
- Credits
- Gift cards
- Refunds
- Order edits
- Quote conversion
The customer should be able to understand which discounts were applied and how the final total was calculated. Internal teams should also be able to explain and support the result.
Reduce the chance of future promotion problems
Helpful controls may include:
- A shared promotion calendar
- Documented eligibility and stacking rules
- A standard review and approval process
- A test matrix for every campaign
- Post-launch monitoring
- Alerts for unexpected discount totals
- Review of promotion usage and margins
- Clear ownership of promotion configuration
- A process for retiring expired rules
Know When to Involve Technical Support
Ecommerce administrators may be able to review search terms, product visibility, enabled shipping methods, promotion eligibility, and basic platform diagnostics.
Changes to search queries, indexes, carrier integrations, custom pricing logic, network settings, or promotion calculations should be reviewed by someone familiar with the platform and connected systems.
When asking for help, provide:
- The exact symptom
- What you expected to happen
- What happened instead
- The affected product, account, order, or promotion
- The customer or user type
- Steps that reproduce the issue
- When the issue began
- Recent releases or configuration changes
- Relevant screenshots, IDs, or diagnostic messages
This context helps the technical team narrow the investigation and reduces the risk of changing unrelated settings.
A Practical Troubleshooting Checklist
When a search, shipping, or promotion problem appears, ask:
- What is the exact customer-facing symptom?
- Who or what is affected?
- Can the issue be reproduced consistently?
- When did it begin?
- What changed shortly before it appeared?
- Which system owns the relevant information?
- Did the information move successfully between systems?
- Are platform settings or business rules changing the result?
- Do logs or diagnostics confirm where the behavior changes?
- Is the problem caused by configuration, data, integration, or custom code?
- How should the experience behave when the underlying service is unavailable?
- What control could detect the issue earlier next time?
A Practical Next Step
Document the exact symptom and trace the relevant information from its source to the customer-facing result. Check one layer at a time and record what you find before making a change.
That approach makes it easier to identify the underlying cause, confirm that the correction worked, and avoid introducing a second issue while addressing the first.
Dealing With a Search, Shipping, or Promotion Issue?
We can help you trace the problem across the data, integrations, platform configuration, and business rules—and identify a practical next step.
Contact us to talk through what you are seeing.
