How to Add Product Weights, Dimension, and SKU Information in Your Ecom Store

Task-specific steps

Weight, dimensions, SKU, inventory, and digital-file settings live on the saved price or variant detail page, not only on the product's first creation screen.

1. 1Go to Payments → Products and create or open the intended product.
2. 2Add at least one price or variant and save the product. A newly added unsaved price is marked New and its detail page is not available until the changes are saved.
3. 3Open the saved price or variant by selecting its linked name or highlighted tile.
4. 4Enter a unique SKU and the correct weight and dimensions using the business's documented units.
5. 5Configure inventory tracking and any variant-specific details. Repeat the process for every size, color, package, or price that requires different physical data.
6. 6Save, reopen the detail page, and verify the product page, order, inventory record, and any shipping process use the intended variant information.

Feature-specific checks

• A parent product value should not be assumed to replace distinct data required for each variant.
• Use a consistent, unique SKU convention and do not silently reuse an identifier assigned to another sellable item.
• Confirm unit conventions before entering dimensions; a correct number in the wrong unit can produce incorrect fulfillment results.

Before you begin

“How to Add Product Weights, Dimension, and SKU Information in Your Ecom Store” is part of the Payments → Products area in Adaptive AI. Create products, prices, and sellable service items. Payment settings can create real charges, invoices, subscriptions, tax records, and customer notifications. Use a controlled test and verify the complete financial record before relying on the setup. The objective is not merely to save a setting; it is to confirm the result works for the staff member or customer who will depend on it.

• Confirm the correct payment provider is connected to the correct business and determine whether you are working in test or live mode.
• Verify currency, price, billing frequency, tax behavior, product or variant details, and customer-facing description.
• Use a clearly labeled internal test customer and avoid using a real customer record while validating a new configuration.
• Review the email, receipt, invoice, estimate, fulfillment, or subscription notifications that the transaction can trigger.
• Confirm your user role permits the intended change and that accounting or fulfillment owners know how the result should be handled.

Verify the result

After completing the instructions in this guide, use a controlled test before treating the setup as finished. A saved screen or success message confirms configuration, but only an end-to-end test confirms the business outcome.

1. 1Preview the customer-facing amount, schedule, terms, product details, and payment method before submitting a controlled test.
2. 2Complete the test and confirm the order, transaction, invoice, estimate, or subscription appears with the expected status.
3. 3Verify the customer record, payment timeline, receipt, internal notification, and connected workflow all contain matching information.
4. 4Check the payment provider or connected accounting system to confirm the same amount, currency, identifier, and status were recorded.
5. 5Validate the next billing date, cancellation behavior, inventory effect, or fulfillment action when the configuration is recurring or product-based.

Troubleshooting checklist

If the result differs from what you expected, preserve the current state and isolate one variable at a time. Start with the checks below before deleting the configuration or rebuilding it from scratch.

• Confirm test and live credentials are not mixed and that the selected product or price belongs to the connected provider account.
• Check required customer fields, currency support, payment-method availability, and any provider decline or validation message.
• Compare Adaptive AI and provider timestamps or identifiers when a payment exists in one system but not the other.
• Review connected workflows and notifications separately from the transaction when payment succeeded but follow-up did not run.
• Do not repeatedly submit a live charge while diagnosing; use logs and a controlled test to avoid duplicate billing.

Best practices

• Use consistent product, price, invoice, and subscription names that make reports and customer statements easy to understand.
• Document refund, cancellation, fulfillment, tax, and failed-payment responsibilities before accepting live transactions.
• Restrict payment-setting access to appropriate staff and review provider connections whenever administrators change.
• Test every new checkout or recurring schedule with the smallest safe test scenario before sharing it publicly.
• Reconcile platform and provider records regularly rather than relying on a single dashboard as the financial source of truth.