Marketplace Automation

Background processing retrieves Amazon listing schemas and a product-type index into company storage, providing the requirement information used by downstream catalogue and listing preparation.

For supported pending marketplace orders or processed orders with a completely withheld delivery address, expand the physical requirements and reserve available stock within the authorised branch and location pool. Supported address retrieval is retried during a limited recovery window; unresolved orders can receive an unknown-route plan for later operational attention without inventing an address.

Create a local collection order using the website's selected branch, product requirements and group components. Later processes send supported picked and completion states back to the connected website.

Update matching item quantities, add or reduce lines and record supported refund or cancellation effects. Where the existing financial records permit, create linked credit or payment entries and release eligible reservations or update the order's operational records.

Create local source-payment and invoice records where the order and financial data allow, then render branded multi-page invoice or credit-note PDFs using saved item, address, currency and tax information. Store the generated document references for later access and printing.

Preserve supplied gross item and shipping amounts while calculating the relevant net and VAT splits from company, product, destination and service settings. Retain marketplace-collected tax separately where supplied. Establish the document's tax country and capture the applicable direct currency-to-headquarters rate at issue time before creating eligible financial records.

For owned product records, use an existing Amazon identifier or prepare a new catalogue submission containing identity, brand, product type, images and attributes. Non-owned products with an existing identifier use the offer-only route. Record the submission result for subsequent listing-status checks.

Calculate offer quantity from stock and pack size, then apply the configured maximum, percentage and buffer settings. Scheduled updates revise quantities and use activation, account and availability settings when managing held offers. At zero stock, configured behaviour can retain an unbuyable offer or remove it.

Derive Amazon prices from country pricing, pack size, configured alterations and rounding. Submit consumer prices and schema-supported business prices or quantity-discount structures, with configured shipping groups resolved to the account's marketplace identifiers.

Scheduled content reconciliation prepares title, description, bullets, ordered images and typed listing attributes from saved data. Where supported, supplied manufacturer, safety and age-related declarations can also be included in the marketplace payload.

Build fixed-price listing submissions from product identity, category, condition, policies, images and description data. For an ended listing, use the available relist route or create a fresh listing where appropriate, retaining the returned listing reference.

Scheduled revision uses changed listing data, calculated stock and local quantity limits to prepare inventory and price updates. Applicable zero-quantity, price, deactivation or restriction conditions can end the listing rather than keeping it active.

Publish updates to title, condition, categories, identifiers, item specifics, policies, images, currency and tax information. Saved description templates combine product data and conditional content when the listing payload is prepared.

Scheduled retrieval collects modified orders and their available buyer, recipient, fulfilment and item information. It records source references, shipping dates and account context, and maps seller product codes to the MS catalogue for later allocation.

Scheduled retrieval collects modified orders with item, address, service and transaction information. Variation product codes are retained where supplied, and multi-leg shipments use the appropriate logistics-provider delivery address while keeping buyer context.

Collect pending orders from connected website databases, map basket products and supplied shipment information, and hand them to the shared order workflow. Subsequent processes can send received, cancelled and shipped statuses back to the website.

Select eligible processed orders with recorded tracking, then send eBay shipment acknowledgement or Amazon shipment confirmation with the supported carrier and item details. Record the resulting transmission status for operational review.

When imported information identifies a fully shipped order, update the supported completion details and release provisional reservations where appropriate. The Amazon-fulfilled route can reconcile eligible local unmet or unshipped quantities as externally fulfilled demand.

The management tools report duplicate product codes across active eBay listings and compare remote quantities with the quantity MS calculates. After reviewing quantity differences, an operator can request their correction through the normal listing synchronisation process.

Retain failed order references for Amazon, eBay and connected websites, reload the available retry list after a restart and retry those orders through their individual retrieval paths. A pending count gives the management process visibility of outstanding import work.

Match or create customer records, prepare addresses and consignment requirements, expand group products into their physical components and select configured shipping-service results. Allocate eligible branch stock using authorised locations; uncovered physical requirements remain back ordered.