The Transaction Records page

This is your command center for everything that moves through Neuro – orders, products, webhooks, rules, plugins, and API calls. Think of it as the black box for your e-commerce operations: when something goes wrong (or right), this is where you see what happened, why it happened, and what to do next.

Use it to monitor, filter, retry, and analyse transaction activity across all your channels in one place.

1. Getting to the Transaction Records Page

To access the Transaction Records page:

1. Open the left-hand navigation menu

2. Click on “Transaction Records”

You’ll land on the main Transaction Records page showing your stores and their connected channels.

Main Page Overview

The main Transaction Records page (/transactionRecords) gives you a high-level view and shortcuts into all your logs:

• Store Selection – Choose which store you want to inspect.

• Search Channels – Quickly find a channel by name.

• Channel List – For the selected store, you’ll see:

  • Channel name

  • Channel ID

  • Platform or provider

  • Activation status (active/inactive checkbox)

  • “View Transaction Records” button to drill into that channel’s logs

At the top-right of the page, three buttons give you direct access to specialised log views:

• API Request Transaction Records – All outbound API calls made by Neuro

• Webhook Transaction Records – Incoming webhook calls (per store)

• Rule Engine Transaction Records – Logs of rule executions and outcomes

From this single screen, you can jump into whichever layer of your integrations you need to investigate.

2. Types of Transaction Records in Neuro

Neuro tracks several kinds of transaction records, each focused on a different layer of your e-commerce stack:

1. Channel Transaction Records – API interactions with sales channels (Shopify, Amazon, eBay, etc.)

2. Plugin Transaction Records – Operations performed by plugins (e.g. 3PLs, WMS, ShipBob - style integrations)

3. API Request Transaction Records – All HTTP requests Neuro sends to external systems

4. Webhook Transaction Records – Webhook calls received from external systems into your stores

5. Rule Engine Transaction Records – When business rules run, what they acted on, and the results

Together, these views give you a complete picture from “customer clicked buy” through to “parcel left the warehouse” and “data reached your accounting platform.”

3. Channel Transaction Records

Channel Transaction Records show you every API interaction between Neuro and a specific sales channel.

Accessing Channel Transaction Records

1. Go to the Transaction Records page

2. Select a store

3. Click “View Transaction Records” next to the channel you want to inspect

Key Features

• Show All Toggle:

  • Off: Only transactions with transferred data

  • On: Includes entries without data transfers (useful for debugging “nothing happened” issues)

• Bulk Retry – Select several failed logs and retry them together

• Individual Retry – Retry a single failed transaction directly from the row

• Table Column Customisation – Choose which columns you care about and hide the rest

Table Columns

• Date – When the transaction happened (filterable by date range)

• Attempts – How many times Neuro tried to complete the transaction

• Status – Waiting, In Progress, Success, Warning, Failed, Info (with colour coding)

• Log Type – The specific operation (e.g. get_orders, submit_fulfillment, push_products)

• Message – Human-readable description or error message

• Actions – Open detailed log view and trigger retry

Use Channel Transaction Records to answer questions like:

• “Did this order actually reach the marketplace?”

• “Why didn’t this product update go live?”

• “What exactly failed at 3 a.m. and did it retry?”

4. Plugin Transaction Records

Plugin Transaction Records work just like channel records, but for plugins such as 3PLs, shipping aggregators or warehouse systems.

Accessing Plugin Transaction Records

1. Open the relevant plugin’s detail page

2. Navigate to its Transaction Records section

Features and Columns

They mirror Channel Transaction Records:

• Show All toggle

• Bulk Retry and individual Retry per row

• Table column customisation

• Same columns: Date, Attempts, Status, Log Type, Message, Actions

Typical Plugin log types include:

• Orders – get_orders, cancel_order, push_orders, missing_order_item

• Inventory – get_quantity, set_inventory_levels, out_of_stock_item

• Fulfilment – prepare_fulfillment_dispatches, fulfillment_webhook

• Location & services – get_fulfillment_centers, get_courier_services, get_tracking_info

Use Plugin logs to pinpoint where data stopped between Neuro and your operational partners.

5. API Request Transaction Records

API Request Transaction Records are your global view of every HTTP API call Neuro makes to external systems.

Accessing API Request Logs

• From Transaction Records, click “API Request Transaction Records”
  or

• Go directly to /transactionRecords/apiTransactionRecords

What You See

• All outbound API calls across channels, plugins, and services

• HTTP method, status code, endpoint URL, response time, and timestamp

Table Columns

• Method – GET, POST, PUT, DELETE, PATCH (filterable)

• Status – HTTP status (200, 404, 500, etc., filterable by number)

• URL – Full endpoint URL with search operators:

  • Equal

  • Contains

  • Starts with

• Response Time (s) – How long the request took (filterable by number/range)

• Date – Timestamp with hour-level precision

• Actions – View detailed JSON request/response (when status is not Waiting and a file exists)

Use API Request logs when you need to see exactly what Neuro sent and how the external system responded.

6. Webhook Transaction Records

Webhook Transaction Records show webhook calls received by your stores from external systems.

Accessing Webhook Logs

1. From Transaction Records, select a store

2. Click “Webhook Transaction Records”
   or go to /transactionRecords/stores/{storeId}/webhooks

Key Features

• Show All Toggle – See only webhooks with transferred data, or everything

• Bulk Retry – Retry multiple failed webhooks together

• Individual Retry – Fix one webhook at a time

• Table Customisation – Show only the columns you need

Table Columns

• Date – When the webhook was received (filterable)

• Attempts – How many times Neuro tried to process it

• Status – Processing status with colours (Waiting, In Progress, Success, Warning, Failed, Info)

• Log Type – Webhook event type

• Message – Description or error message

• Actions – Open detailed payload view and/or retry

Use Webhook logs when a system says “we sent it,” and you need to see what actually arrived.

7. Rule Engine Transaction Records

Rule Engine Transaction Records let you trace exactly what your business rules did and why.

Accessing Rule Engine Logs

• From Transaction Records, click “Rule Engine Transaction Records”
  or go to /transactionRecords/rules

Key Features

• Refresh Button – Manually update the list for near real-time monitoring

• Data Reference Links – Click through to the entity that triggered the rule (order, product, etc.)

• Table Customisation – Configure which fields you want to see

Table Columns

• Date – When the rule ran (filterable)

• Data Reference – Type and ID of the entity involved, with a clickable link

• Trigger Type – Manual, Event, or Triggered by Rule (filterable)

• Triggered By – The user or rule that initiated the execution

• Status – Waiting, In Progress, Success, Warning, Failed, Info

• Actions – Open detailed execution log (when file exists and status is not Waiting)

Use Rule Engine logs to debug “smart” behaviour: automated decisions, conditional flows, and chained rules.

8. Common Table Headers at a Glance

Across the different record types, you’ll see a familiar pattern of columns:

Channel & Plugin Records

• Date – When it happened (date-range filter)

• Attempts – How many times it was retried

• Status – Operational state of the transaction

• Log Type – The type of operation

• Message – Explanation or error text

• Actions – View details, retry where supported

API Request Records

• Method – HTTP verb

• Status – HTTP status code

• URL – Endpoint called

• Response Time (s) – Performance insight

• Date – Timestamp with hour precision

• Actions – View JSON details

Webhook Records

• Date – Webhook received time

• Attempts – Processing attempts

• Status – Processing status

• Log Type – Webhook event type

• Message – Description/error

• Actions – View details, retry

Rule Engine Records

• Date – Rule execution time

• Data Reference – Entity involved

• Trigger Type – How the rule was fired

• Triggered By – Who or what triggered it

• Status – Rule execution outcome

• Actions – View details

Once you recognise these patterns, switching between log types becomes second nature.

9. Log Types: What’s Actually Happening Under the Hood

Log Types tell you what kind of operation a transaction represents. Neuro supports a large catalogue of log types; here are the main categories.

9.1 Channel Log Types (Examples)

Authentication & Tokens

• auth_connect, access_tokens, refresh_tokens, restricted_tokens, token_exchange, verify_scopes, change_scopes

Orders

• get_order, get_orders, get_order_items, get_order_details, get_order_updates, get_order_notes

• create_order, update_order, update_order_status

• mark_as_downloaded_order, mark_as_shipped_order, dispatch_order, process_order, sync_orders

• get_cancelled_orders, get_restrict_location_orders, get_pos_orders

Fulfilment

• get_fulfillment_order, get_order_fulfillment_result

• submit_fulfillment, submit_partial_fulfillment, submit_fulfillment_tracking_event

• prepare_fulfillment_dispatches, prepare_fulfillment_event_dispatches, prepare_partial_fulfillment_dispatches

• check_fulfilled_order_fulfillment, create_shipment, register_shipment, submit_shipment_tracking

Products

• get_products, get_product_detail, get_product_images, get_product_variants, get_product_attributes

• get_product_price, get_product_stocks, get_metafields

• push_products, prepare_push_products, sync_products, import_products

• update_product_stock, deactivate_product, reactivate_product

Inventory

• get_inventory_levels, get_inventory_items, get_stock_item

• set_inventory_levels, submit_inventory, submit_stock, submit_variant_inventory

• prepare_inventory_dispatches, prepare_all_inventory_dispatches, remove_missing_inventory_levels

Feeds & Reports

• submit_feed, get_feed, get_feed_submission_list, get_feed_submission_result, get_feed_submission_detail, check_feeds

• request_products_report, get_report_request_list, get_report, get_report_document, check_reports

Invoices

• get_invoice, create_invoice, auto_create_invoice, submit_invoice

• push_invoices, prepare_push_invoices, prepare_invoices, push_invoice_notes

Customers & Addresses

• get_customer, create_customer, create_contact

• get_billing_address, get_shipping_address

Locations & Stores

• get_shipping_providers, get_delivery_options, get_locations, get_countries, get_states, get_warehouses

• get_stores, create_store, update_store, delete_store, update_store_status, store_info, sync_store

Webhooks & Other Operations

• create_webhook, cancel_webhook, inbound_webhook_log, shopify_webhook_log

• get_channels, get_accounts, get_carrier, get_currency, get_currency_code, get_suppliers, get_tax_types

• get_process_status, get_process_status_dispatches, check_sku, prepare_check_sku

• Returns, refunds, pickups, purchase orders and confirmation flows:

  • calculate_return, submit_return, prepare_return_dispatches, submit_refund

  • submit_pickup, prepare_pickup_orders, create_charge

  • create_purchase_orders, prepare_purchase_order_transactions, purchase_order_check_transaction

  • confirmation_order_check_transaction, prepare_confirmation_order_transactions

  • prepare_acknowledgements_despatches, submit_acknowledgements

• channel_migrate, notify_refresh_tokens

Tip:

The Log Type filter accepts custom values, so you can type in any log name even if it’s not shown in the dropdown.

9.2 Plugin Log Types (Examples)

Authentication

• access_tokens, auth_connect, refresh_tokens, register_token_exchange

Orders

• get_orders, get_returned_orders, cancel_order, prepare_cancel_orders

• push_order, push_orders, push_order_items, prepare_push_orders, missing_order_item

Products & Inventory

• push_product, push_products, get_product_categories

• get_quantity, set_inventory_levels, prepare_inventory_dispatches, out_of_stock_item

Fulfilment & Webhooks

• prepare_fulfillment_dispatches

• fulfillment_webhook, inventory_webhook, create_shipped_webhook

Locations & Services

• get_channels, get_clients, get_courier_services, get_delivery_ways

• get_fulfillment_centers, get_locations, get_suppliers, get_warehouses, get_tracking_info

You don’t need to memorise these; understanding the category (orders, inventory, fulfilment) is usually enough to make sense of what’s happening.

10. Filtering and Searching Transaction Records

With large volumes of data, filters are your best friend.

10.1 Date Filter

Available everywhere:

• Channel / Plugin / Webhook / Rule Engine Logs – Filter by date range

• API Request Logs – Filter by date and hour

How to use:

1. Click the filter icon in the Date column

2. Pick a start and end date (and hour for API logs)

3. Click Apply

10.2 Status Filter

Works across all transaction types:

• Waiting, In Progress, Success, Warning, Failed, Info

Use it to focus on:

• Only Failed and Warning to triage issues

• Only Success to confirm a fix worked

10.3 Log Type Filter

Available for:

• Channel logs

• Plugin logs

• Webhook logs

Filter by any known log type or type a custom value directly.

10.4 Search

Search behaviour varies by log type:

• Channel / Plugin Logs – Search inside the Message

• API Request Logs – Search by related IDs

• Rule Engine Logs – Search by Data Reference

Simply type in your search term; results refine as you type.

10.5 API-Specific Filters

• Method – Filter by GET, POST, PUT, DELETE, PATCH

• Status (HTTP) – Filter by HTTP status code (e.g. 500)

• URL – Use equal, contains, or starts with to match endpoint patterns

• Response Time – Use numeric filters to spot slow requests

10.6 Rule Engine Filters

• Trigger Type – Manual, Event, Triggered by Rule

• Data Reference – Filter by entity ID or type

10.7 Show All Toggle

Available on:

• Channel, Plugin, and Webhook logs

• Default: Only show transactions with transferred data

• Show All: Include “empty” or metadata-only entries

10.8 Clear All Filters

If things look odd:

• Click “Clear All” in any filter dropdown

• Or manually clear each filter to reset the view

11. Viewing Log Details

When you need to go deep on a single transaction, open the Log Viewer.

Accessing the Log Viewer

• Click the pencil icon in the Actions column for the transaction you want to inspect

Tabs You May See

• Log Content – JSON with syntax highlighting, folding, copy, and search

• AI Suggestion – When available, shows suggested fixes or next steps

• Response XML – XML responses, folded and highlighted

• Request XML – XML requests

• Request GraphQL – GraphQL queries with structure highlighting

Log Viewer Tools

• Fold/Unfold All – Quickly collapse or expand everything

• Copy to Clipboard – Copy entire logs or sections for support/dev teams

• Syntax Highlighting – Makes complex payloads easier to read

• Reset Fold State – Start fresh if you’ve expanded a lot

• Search Within Log – Jump straight to the field or ID you care about

12. Retry Functionality

Sometimes a failure is temporary. Instead of redoing work manually, you can ask Neuro to try again.

12.1 Individual Retry

Available for:

• Channel Transaction Records

• Plugin Transaction Records

• Webhook Transaction Records

How to use:

1. Filter to Failed or Warning status

2. Click the Retry icon for the chosen log

3. The system re-executes the transaction and updates the status

12.2 Bulk Retry

When many similar failures occur (for example, a brief outage):

1. Select multiple rows using the checkboxes

2. Click “Bulk Retry”

3. Confirm the operation

Neuro will attempt all selected retries and update each status individually.

12.3 Retry Limitations

• API Request Logs – Do not support retry; they are read-only traces

• Rule Engine Logs – Do not support retry; rules run based on triggers

• Only logs that support retry will show the retry option

• Bulk retries may be rate-limited to protect performance

13. Table Customisation

Every team pays attention to different details. You can customise tables to match your workflow.

How to Customise

1. Click the column icon in the top-right of any transaction table

2. In the dialog:

   • Toggle columns on or off

   • Drag and drop to reorder columns

Customisation is stored per table type:

• Channel Logs

• Plugin Logs

• API Logs

• Webhook Logs

• Rule Engine Logs

Your preferences are saved automatically and persist across sessions, with an option to reset to defaults at any time.

14. Troubleshooting with Transaction Records

When something isn’t working, Transaction Records are usually the fastest path to an answer.

Logs Not Appearing

• Check the Show All toggle

• Clear filters that may be too strict

• Confirm you’ve selected the correct store/channel

• Widen the date range

Retry Failures

• Make sure the log type supports retry

• Check whether the underlying issue is fixed (credentials, rate limits, system downtime)

• Inspect the log details for error messages

• Try a single retry before bulk retry

Log Viewer Not Loading

• Confirm the log has file content (has_file and status not Waiting)

• Refresh the page or try another browser

• Clear cache if the issue persists

Filters Not Behaving As Expected

• Clear all filters and start again

• Check for typos in custom log types

• Verify date ranges and numeric filters

Performance Issues

• Narrow the date range

• Apply more specific filters (status, log type, store)

• Avoid Show All on very large datasets

15. Status and HTTP Method Reference

Status Colours

HTTP Methods

16. Getting Help

If you get stuck:

1. Check the Log Viewer for error messages and payload details

2. Use filters and search to narrow down the issue

3. Retry where appropriate for transient errors

4. Contact Neuro Support with:

   • Transaction record ID(s)

   • Screenshots of errors

   • Copy of log details

   • Steps to reproduce

   • Store and channel information

By bringing channel logs, plugins, APIs, webhooks, and rules into one place, the Transaction Records page turns your e-commerce operations from “mystery box” into “control panel.” Use it as your everyday dashboard for spotting issues early, fixing them fast, and proving that data really did what it was supposed to do.