Skip to main content

Implementation QA Checklist

Ensuring your implementation is ready to go live

Updated over a month ago

Background

This QA checklist helps you test a typical e-commerce, B2C implementation of iPaaS.com. While not exhaustive, it provides guidance for creating a comprehensive test plan before going live.

NOTE: Not every feature described here is supported by every integration.

Prerequisites:

  • Completed iPaaS.com training

  • Understanding of customer requirements for iPaaS.com usage

  • Experience with e-commerce sites and integration testing

  • Familiarity with integration capabilities and mapping collections

Note: This document will be updated as more implementations are completed. Please check for the latest version.


Overview

Test data flow through each mapping collection to ensure it enters iPaaS.com and reaches destination systems as intended.

Key Testing Considerations

  1. Positive and Negative Testing

    • Test data that meets filter criteria

    • Test data that should be excluded by filters

  2. Bi-directional Sync

    • Carefully test to ensure only the intended data is overridden

    • Note: Capability depends on the integration

  3. Data Linkages

    • Categories assigned in one system should transfer to another

    • Customer/company links to transactions should be maintained

    • Test with existent and non-existent data

  4. User States

    • Test both guest and logged-in states

    • Place test orders in both states for e-commerce sites

  5. Delete Operations

    • Test delete mapping collections where applicable

    • Important: Delete mappings are crucial for data hygiene and preventing duplicate data issues

  6. Data Transformation

    • Verify that dynamic formulas work as expected

    • Test with sufficient data variety

Items Not Covered Below

  • Delete mappings

  • Product categories

  • Customer categories

  • Variant options


Data Models

Follow this order to minimize dependency issues. You may need to revisit sections if errors occur (e.g., discovering a missing shipping method during order testing).

1. Locations

Test: Ensure all locations are created (manually or via initialization) and connected via external ID when applicable.

Note: Create and link location groups if needed.

2. Payment Methods

Test: Ensure all payment methods are created and connected via external ID when applicable.

3. Shipping Methods

Test: Ensure all shipping methods are created and connected via external ID when applicable.


Products

Product Creation

Where: Product source of truth system (typically ERP, sometimes POS)

Test Different Product Types:

  • Simple, variant, kit products

  • Products with various options

  • Products with custom fields

  • Different tax classifications

  • Category assignments

  • Varied inventory levels across locations

Verify:

  • Correct appearance in iPaaS.com and destination systems

  • Accurate inventory and display rules

  • Proper category assignment

  • Custom field population

  • All field values are as intended

  • Variants show with correct options

Product Updates

Test Updates For:

  • Different product types

  • Variant modifications (add/remove options with inventory)

  • Custom field changes

  • Tax classification updates

  • Category additions/removals

  • Inventory level adjustments (including setting Qty on Hand and Qty Available to 0)

  • Show/hide product rules

Verify:

  • All product header fields were updated correctly

  • Inventory accuracy

  • Category updates

  • Display rules functioning

  • Custom field updates

Repeat tests if multiple platforms support product operations.


Customers

Customer Creation

Where: Customer source of truth system (e-commerce platform, CRM, etc.)

Test Variations:

  • Different names and email addresses

  • With and without order links

  • Customer/company relationships

  • Primary billing/shipping addresses

  • Category assignments

Verify:

  • Core details (name, email) transfer correctly

  • Order linkages (if configured)

  • Relationship accuracy

  • Address designations

  • Category assignments

  • Dynamic formula transformations

Customer Updates

Test Updates For:

  • Name and email changes

  • Order linkage modifications

  • Relationship updates

  • Address changes

  • Category modifications

Verify: Same points as creation testing

Repeat tests if multiple platforms support customer operations.


Transactions

Transaction Creation

Where: Transaction source of truth system (e-commerce platform, ERP, etc.)

Test Scenarios:

Tax Testing:

  • Taxable orders (test codes and rules)

  • Non-taxable orders

Line Items:

  • Line item discounts

  • Gift card purchases

  • Mixed product types

Payments:

  • Each payment type (especially gift cards)

  • Multiple payment types per transaction

  • Authorize and capture flows

  • Name-mapped payment methods

Shipping:

  • Each shipping method

  • BOPIS orders (when applicable for all available stores)

  • Mixed shipping

  • Name-mapped shipping methods

Additional Elements:

  • Addresses

  • Notes (with and without)

  • Related documents

  • Custom fields

Verify:

  • Customer/company linkages

  • Header value accuracy

  • Line items and discount application

  • Payment processing (including gift card balances)

  • Address designations

  • Notes and documents

  • Custom fields

  • Dynamic formula transformations

Transaction Updates

NOTE: Not all systems allow full or partial transaction updates.

Test Updates For:

  • Header updates (triggered by line item changes)

  • Tax modifications

  • Line item additions/removals

  • Discount changes

  • Payment capture flows

  • Tracking ID additions

  • Address updates

  • Note modifications

  • Document changes

  • Custom field updates

  • Shipping method changes

  • BOPIS/shipping conversions

  • Cancellations

  • Refunds

Verify: Same points as creation testing

Repeat tests if multiple platforms support transaction operations.


Final Steps

Once all tests pass, you can:

  1. Enable webhooks.

Remember to document any issues discovered and retest affected areas after fixes are implemented.

Did this answer your question?