{"id":22460,"date":"2024-06-17T12:45:18","date_gmt":"2024-06-17T12:45:18","guid":{"rendered":"https:\/\/synder.com\/help\/?p=22460"},"modified":"2026-05-11T13:47:48","modified_gmt":"2026-05-11T13:47:48","slug":"summary-sync-for-ecommerce-things-you-need-to-know","status":"publish","type":"post","link":"https:\/\/synder.com\/help\/summary-sync-for-ecommerce-things-you-need-to-know\/","title":{"rendered":"Summary Sync for Ecommerce: Things You Need to Know"},"content":{"rendered":"\n
This guide explains how<\/strong> Synder aggregates e-commerce and payment gateway data into summaries<\/strong>, the structure of mapping, and what to expect during reconciliation.<\/p>\n\n\n\n Use this guide to understand:<\/p>\n\n\n\n This guide outlines various scenarios demonstrating how Synder processes multichannel data in Summary Sync, using Shopify as the e-commerce platform and Stripe as the payment gateway for illustration. It focuses on behavior and use cases rather than step-by-step instructions.<\/strong><\/p>\n\n\n\n <\/p>\n\n\n\n E-commerce businesses typically use:<\/p>\n\n\n\n Each platform stores different pieces of financial data:<\/p>\n\n\n\n For accurate accounting, fully capture and reconcile all sales components. Synder aggregates this data into structured summaries, providing better visibility and easier management.<\/p>\n\n\n\n <\/p>\n\n\n\n For Synder to aggregate ecommerce data properly, connect<\/strong> all platforms involved in your money flow<\/strong>.<\/p>\n\n\n\n During onboarding, select every platform involved in processing your sales and payments <\/strong>(learn more about onboarding steps here<\/a>).<\/p>\n\n\n\n For example, if you sell on Shopify and accept payments via Shopify payments, Stripe, PayPal, and Authorize.net<\/a>, connect all of them. <\/p>\n\n\n\n You will need to:<\/p>\n\n\n\n When connecting integrations, Synder asks you to select a \u201cFrom\u201d date<\/strong> for data import. This date must match across the E-commerce platform\/s and all related payment gateways.<\/p>\n\n\n\n <\/p>\n\n\n\n As a result, if Shopify orders between July 1 and 4 were paid via Stripe, they will not be imported. Because of this, you will see discrepancies in your financial reports. <\/p>\n\n\n\n Best practice is to always select the same import start date for e-commerce platforms and their gateways<\/strong>.<\/p>\n\n\n\n <\/p>\n\n\n\n If you connect a payment gateway after onboarding:<\/p>\n\n\n\n This is an expected behaviour – Synder needs some time to process and aggregate it in the best way. During this process, Synder is:<\/p>\n\n\n\n After completion, summaries will change the status to \u201cFully fetched<\/strong>\u201d, indicating that all available data for that period has been aggregated. At this stage, the summaries are ready for review and synchronization.<\/p>\n\n\n\n <\/p>\n\n\n\n When a payment processor (e.g., Stripe) is used exclusively for Shopify orders, Synder aggregates all transactions processed by both Shopify Payments and Stripe into a single summary.<\/p>\n\n\n\n Follow these steps to check and confirm this behaviour:<\/p>\n\n\n\n <\/p>\n\n\n\n If Stripe is used for Shopify orders as well as non-Shopify transactions (manual payments, invoices, etc.), Synder creates: This separation ensures that E-commerce revenue is not mixed with other sales and that financial reports remain accurate.<\/p>\n\n\n\n <\/p>\n\n\n\n Mapping is an essential part of summary aggregation. It defines the final result of financial data synchronization to your books and ensures accurate reports. This tab includes all E-commerce platform as well as all related gateway mapping lines. Columns:<\/p>\n\n\n\n If multiple gateways are used for e-commerce sales, you will see separate mapping lines for each gateway under the e-commerce integration tab. <\/p>\n\n\n\n This allows you to:<\/p>\n\n\n\n Note:<\/em><\/strong> Synder identifies \u201cEcommerce vs. Gateway\u201d relations between platforms during data import. If a new gateway starts processing your e-commerce orders, new mapping lines appear automatically.<\/p>\n\n\n\n This tab appears only<\/strong> if the gateway processes non-ecommerce transactions. Columns:<\/p>\n\n\n\n This helps identify whether the sales data is coming directly from the processor or if it is related to the E-commerce platform sales. <\/p>\n\n\n\n If a gateway processes only e-commerce-related payments, its standalone tab remains empty.<\/p>\n\n\n\n <\/p>\n\n\n\n Reconciling your e-commerce summaries is very straightforward with the e-commerce flow. <\/p>\n\n\n\n (e.g., Shopify Finances Summary<\/strong>).<\/p>\n\n\n\n In instances where Stripe handles various payments from different platforms, refer to the Stripe balance summary report<\/strong> to compare and reconcile these figures. For a step-by-step Stripe summary reconciliation guide, please refer to this article<\/a>. <\/p>\n\n\n\n <\/p>\n\n\n\n <\/p>\n\n\n\n Reach out to Synder Team<\/em><\/a> <\/strong>via online support chat or email with any questions you have \u2013 we are always happy to help you!<\/p>\n","protected":false},"excerpt":{"rendered":" Overview: E-commerce accounting challenges How to connect platforms correctly for accurate aggregation How Synder aggregates E-commerce data into summaries: Core principles What to expect on the Mapping page How to reconcile E-commerce summaries Important notes FAQ This guide explains how Synder aggregates e-commerce and payment gateway data into summaries, the structure of mapping, and what […]<\/p>\n","protected":false},"author":2,"featured_media":0,"comment_status":"open","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"inline_featured_image":false,"_et_pb_use_builder":"","_et_pb_old_content":"","_et_gb_content_width":"","advgb_blocks_editor_width":"","advgb_blocks_columns_visual_guide":"","footnotes":"","_ppma_block_editor_authors":""},"categories":[377,376,398],"tags":[],"ppma_author":[341],"class_list":["post-22460","post","type-post","status-publish","format-standard","hentry","category-overview","category-transaction-recording-summary","category-ecommerce-integrations-main"],"yoast_head":"\n\n
Overview: E-commerce accounting challenges<\/h2>\n\n\n\n
\n
<\/li>\n\n\n\n
<\/li>\n\n\n\n\n
<\/li>\n\n\n\n
<\/li>\n<\/ul>\n\n\n\nHow to connect platforms correctly for accurate aggregation<\/strong><\/h2>\n\n\n\n
\n
<\/figure>\n\n\n\n\n
or<\/strong><\/li>\n\n\n\n
<\/figure>\n\n\n\n\n
<\/figure>\n\n\n\nExample scenario on why the consistent import date is critical:<\/strong><\/h3>\n\n\n\n
\n
What happens if a new gateway connect<\/strong>s later<\/strong><\/h3>\n\n\n\n
\n
<\/figure>\n\n\n\n\n
<\/figure>\n\n\n\nHow Synder aggregates E-commerce data into summaries: Core principles<\/strong><\/h2>\n\n\n\n
1. E-commerce orders and related gateway payments are included under one summary<\/strong><\/h3>\n\n\n\n
\n
\n
<\/figure>\n\n\n\n
<\/figure>\n\n\n\n2. Standalone gateway activity is separated<\/strong><\/h3>\n\n\n\n
<\/p>\n\n\n\n\n
<\/figure>\n\n\n\nWhat to expect on the Mapping page<\/strong><\/h2>\n\n\n\n
There are two types of integration views in the Mappings list:
<\/p>\n\n\n\n\n
\n
<\/figure>\n\n\n\n\n
\n
\n
<\/figure>\n\n\n\n
<\/figure>\n\n\n\nHow to reconcile E-commerce summaries<\/strong><\/h2>\n\n\n\n
\n
\n
\n
\n
<\/figure>\n\n\n\n\n
<\/figure>\n\n\n\n
Note:<\/em><\/strong> It\u2019s important to exclude<\/strong> the Stripe payments of E-commerce orders in your Stripe report so the number can be reconciled against Synder\u2019s Stripe summary for the day.<\/p>\n\n\n\n
<\/figure>\n\n\n\nImportant notes<\/strong><\/h2>\n\n\n\n
\n
<\/li>\n\n\n\nFAQ<\/strong><\/h2>\n\n\n\n
\n
This usually means Stripe is processing <\/em>both e-commerce and non-ecommerce transactions<\/em><\/strong>. Synder separates these into different summaries, so only the ecommerce-related Stripe activity is included in the Shopify summary.<\/em>
<\/li>\n\n\n\n
When you connect a new gateway and initiate import, Synder re-evaluates previously created summaries to cross-check if any transaction is related to an E-commerce order. If there are such transactions, Synder will need to rebuild some summaries. During this time, summaries may appear as <\/em>Not Ready\/Fetching<\/em><\/strong>.<\/em>
<\/li>\n\n\n\n
No, Synder will not make any change to the already synced data. If you need the data within the summary to be adjusted, you need to rollback the summary, rebuild, and sync again. <\/em>
<\/em>
<\/em><\/li>\n<\/ol>\n\n\n\n