Pepperfry Marketplace Reconciliation Using OMS

Cointab helps finance teams reconcile Pepperfry marketplace data against OMS records using a structured Side A / Side B workflow. The goal is simple: compare the records your business expects to be correct with the records received from the marketplace, identify differences clearly, and export audit-ready reconciliation reports.

This use case is especially relevant for furniture and home-furnishing sellers who manage high order volumes, multiple order statuses, cancellations, shipping updates, settlements, and payment references across systems. Instead of relying on Excel formulas and repeated manual checks, teams can upload the required files, map fields once, and run the same reconciliation setup for future periods.

What this reconciliation covers

In a Pepperfry marketplace reconciliation, your internal OMS data usually acts as Side A, while Pepperfry reports act as Side B.

Side A: Your OMS records

Typical OMS data may include:

• Order ID
• Order date
• SKU or product reference
• Order amount
• Shipping or fulfillment status
• Cancellation status
• Return or adjustment details
• Internal payment or settlement reference

Side B: Pepperfry reports

Typical marketplace files may include:

• Order detail report
• Shipping details report
• Cancelled order report
• UTR or payment reference report
• Settlement or invoice-style report

Cointab lets teams compare these records by order identifier, amount, date, reference fields, or other mapped columns depending on how the reports are structured.

Why Pepperfry reconciliation matters

Marketplace finance teams need a reliable way to confirm that internal OMS records align with marketplace-reported activity. When records do not match, the issue may be caused by:

• Missing order rows in one of the reports
• Amount differences between OMS and marketplace records
• Cancelled orders appearing differently across files
• Settlement references not linking cleanly to order records
• Shipping or fulfillment updates arriving later than sales data
• File format changes that break manual Excel checks

Without a structured process, these issues can remain open for too long. That can make month-end close, partner follow-up, and audit preparation harder than necessary.

How Cointab handles the workflow

Cointab follows a clear reconciliation process that finance teams can reuse.

1. Create a Pepperfry reconciliation in a team workspace.
2. Upload the required OMS and Pepperfry files, or configure automated data input.
3. Map the important fields such as order date, amount, and identifier columns.
4. Add supporting files if needed for lookups or enrichment.
5. Create derived columns when the report needs cleaning or calculation.
6. Run reconciliation manually or on a schedule.
7. Review the report dashboard and inspect matched and open items.
8. Download the Excel report for review, audit, or follow-up.

The same setup can be reused in future periods, which reduces repeated configuration work and keeps reporting consistent across runs.

Matching logic for OMS to marketplace reconciliation

Cointab uses structured matching logic to compare transactions across both sides. This is useful when one report line may correspond to one or more lines on the other side, or when identifiers are incomplete or slightly different.

The reconciliation engine supports cases such as:

• One-to-one matching
• One-to-many matching
• Many-to-one matching
• Many-to-many matching
• Net-to-net comparison
• Partial matching
• Contra-style adjustments

For Pepperfry and OMS workflows, that means the system can compare order references, settlement references, amounts, and other identifiers while still keeping unmatched items visible for review.

What the reconciliation report shows

Once the run is complete, Cointab shows a report dashboard with clear transaction categories.

Fully matched

These are orders or transactions where the relevant identifiers and amounts align according to the configured logic.

Partially matched

These are records where the identifiers appear to relate, but the amounts do not fully match. This is useful when the order exists in both systems, but there is a difference that needs review.

Unmatched

These are records present on one side but not found on the other. For example:

• Present in OMS but missing in Pepperfry
• Present in Pepperfry but missing in OMS
• Present in one file but not linked by the configured identifier logic

Skipped

Skipped records are not included in the comparison because they were incomplete, invalid, duplicate, or excluded by rule. Keeping them visible helps finance teams understand what was left out and why.

Data setup for Pepperfry and OMS files

Cointab works with CSV, XLS, and XLSX files. For each primary report, teams can define:

• Header row
• Date column
• Amount column
• Identifier column or columns

Common identifiers may include order ID, transaction ID, settlement ID, payment reference, or shipping reference. If the file format changes, the system can reject it with a clear format error so the issue is easy to identify.

Supporting data can also be uploaded when needed. These files are not reconciled directly, but they can help enrich or calculate the primary data before matching. Examples include product masters, mapping files, fee files, or return reports.

Derived columns for cleaner comparisons

Some marketplace files need additional calculation before reconciliation. Cointab supports derived columns so teams can normalize data without rebuilding spreadsheets each period.

Examples include:

• Clean order ID
• Net amount
• Refund amount as negative
• Combined reference field
• Amount after fee
• Delivered payment amount
• Normalized transaction ID

Users can create derived columns with AI assistance by describing the logic in plain language. That makes it easier to prepare the data without manually writing formulas.

Handling open items and exceptions

After structured matching is complete, Cointab helps teams focus on the remaining exceptions.

This is useful when:

• An order is present in OMS but missing from Pepperfry data
• The amount differs across systems
• A record appears to match, but the reference is incomplete
• A later file needs to be added before the report is final

Users can also manually match transactions if the business context is clear and the totals tally. Manual matches remain auditable and can be reviewed later.

Reconciliation reuse and automation

Pepperfry reconciliation is often a recurring process, so reuse matters.

Once the workflow is set up, teams can run it again for future periods without rebuilding the same rules. Cointab can also automate file receipt and reconciliation using email, SFTP, or API-based data flow where needed.

That makes it possible to support:

• Daily reconciliation
• Weekly reporting
• Monthly close workflows
• End-of-period settlement checks
• Ongoing exception tracking

If a file is received late, users can upload the missed file under the same reconciliation and refresh the report.

Why finance teams use a structured workflow instead of Excel

A spreadsheet can work for small volumes, but marketplace reconciliation becomes harder as the number of orders, files, and exceptions grows. Cointab helps teams replace repeated manual comparisons with a workflow that is easier to trace and reuse.

The main advantages are:

• Consistent matching logic
• Clear matched and unmatched categories
• Better handling of large files
• Faster exception review
• Reusable setup for future periods
• Downloadable Excel reconciliation reports
• Shared workspace with team visibility

Typical use cases within the Pepperfry workflow

This reconciliation approach can help with:

• OMS order validation against Pepperfry order data
• Settlement and payment reference checks
• Cancellation and shipping status review
• Amount difference analysis
• Missing transaction detection
• Audit and month-end reporting

For finance teams, the value is not just in matching records. It is in seeing what matched, what did not, and what action is needed next.

FAQ

What files are usually needed for Pepperfry reconciliation?

Most teams use an OMS export on one side and Pepperfry order, shipping, cancellation, and payment or settlement files on the other side. The exact file list depends on the workflow being reconciled.

Can Cointab handle amount differences between OMS and Pepperfry?

Yes. Partially matched transactions are surfaced clearly so teams can review amount differences instead of treating them as a simple pass or fail.

What happens if a file was missed earlier?

The missed file can be uploaded under the same reconciliation, and the report can be refreshed so the new data is included in the comparison.

Can this reconciliation be reused for future periods?

Yes. Once configured, the same reconciliation setup can be reused for later runs, which reduces repeat work and keeps reporting consistent.

Can open items be reviewed manually?

Yes. Users can inspect open transactions, apply manual matches where appropriate, and keep the process auditable for internal review.