PROCESS RITE · PAYMENT WORKFLOW GUIDE
Retail Ecommerce Payments: Stock, Pickup, Shipping and Returns
Plan online checkout around catalogue ownership, available stock and fulfilment. Verify the full connection to your store before changing platforms or payment providers.
In this guide
Choose which system owns products, stock and orders
A retail website should not become a second, conflicting version of the store. Identify the system that owns product identifiers, prices, available quantity and order status. Decide which fields can be edited in the website and which must be maintained elsewhere. A connector that imports product names may not synchronise stock, refunds or customer records.
Draw the path from a customer adding an item to the cart through payment, picking, fulfilment and settlement. Mark every application involved and the person responsible for each handoff. Use that map to request a demonstration of the exact website platform, software plan, POS and connector. A generic statement that two brands integrate is not enough to establish the proposed workflow.
Make the online catalogue usable and maintainable
Start with a small catalogue containing an ordinary item, a size or colour variant, a multipack and a product with a special handling requirement. Check that identifiers remain stable between the store and website. A pack should not silently share the same quantity meaning as a single unit if that would make inventory inaccurate.
Use clear product descriptions, appropriate images and accurate fulfilment information. Avoid publishing supplier data without checking what the store actually carries. Establish who approves price changes, removes discontinued items and investigates duplicate products. Test what happens when a product is renamed or a variant is retired; historical orders should remain understandable even after the catalogue changes.
Verify available stock under simultaneous sales
The same last item may be viewed by a website shopper while a counter customer is buying it. Ask when stock is reserved and how quickly changes reach each channel. Confirm whether the integration is immediate, periodic or manual, and what happens if the connection fails. Do not advertise real-time inventory unless the specific arrangement has been verified.
Demonstrate the last available unit being sold in the store while an online cart contains it. Then test cancellation, a returned item and a stock correction. Establish who resolves oversold orders and how customers are contacted. If synchronisation is limited, choose a practical stock buffer or review process that the business can maintain rather than relying on a feature name alone.
Configure prices, discounts and charges deliberately
Have the owner approve the catalogue, promotions and charge configuration, with appropriate advice for tax treatment. Check whether online and counter prices are intended to match. Test an order with a discounted item, a delivery or pickup charge where applicable and a promotion that excludes certain products. Confirm the total shown before payment and the values on the receipt.
Bundles and partial returns need particular attention. If a customer returns one item from a discounted bundle, ask how the approved return policy is represented. Verify which application recalculates the amount and whether staff can override it. Keep the configuration and permission rules documented so an employee does not create an inconsistent adjustment simply because the checkout screen permits it.
Design pickup as an operational handoff
Specify who receives new pickup orders, how items are reserved and when the customer receives a ready-for-pickup message. An order confirmation should not imply that staff have already picked and checked the goods. Use distinct statuses that employees and customers can understand, and confirm whether notifications are automatic or require an authorised staff action.
Test a missing item, a customer arriving early and an order not collected within the store’s policy. Define the verification procedure for handing goods to the customer or an authorised collector. Record completion so another employee does not prepare the order again. Confirm cancellation and refund steps separately; changing a fulfilment status does not necessarily return the payment.
Connect shipping information to the paid order
For shipped orders, confirm how staff receive the delivery details, choose a supported shipping method and record dispatch. The customer should see the applicable charge and delivery information before committing. Avoid presenting an estimated dispatch or delivery period as a guarantee unless the business can support that commitment.
Use a test order containing more than one item and verify the picking list, parcel contents, order reference and tracking notification where supported. Demonstrate a split shipment if the business needs it. Determine how a changed address is authorised and recorded. Payment approval alone is not a complete fulfilment check, and a printed shipping label does not prove that the parcel has left the store.
Confirm payment-platform compatibility before switching
Identify the payment services supported by the actual website platform, plan and checkout arrangement. A store’s existing terminal account cannot necessarily be attached to every hosted ecommerce product. Ask the proposed provider to demonstrate the supported connection and identify who bills for the platform, gateway, processing and any required application.
If considering Clover® alongside online selling, verify the exact connector, catalogue ownership and refund path. Do not assume that selecting a Clover device establishes every online capability. Keep the required hardware, software plan, applications and processing relationship together in the written proposal so the business can review the whole configuration.
Test mobile checkout beyond the home screen
Use the links and devices customers actually use, including an ordinary mobile browser. Check product selection, variant controls, address entry, delivery choice, payment entry, errors and confirmation. Fields should remain readable without sideways scrolling, and the final total should be visible before payment. Test returning from any external payment page.
Where a wallet or other payment method is supported, verify it in the actual configuration and browser being tested. Do not advertise it solely because a platform mentions it generally. Test a declined payment and an interrupted checkout. A failed attempt should not produce an order that staff mistake for fully paid, and refreshing a confirmation page should not create another collection.
Separate payment status from order status
An order may be created before payment succeeds, while a payment may succeed before an integration finishes updating the order. Define which status permits staff to fulfil and how they check uncertain results. Use the provider’s actual labels and supported procedure rather than assuming every platform uses “paid,” “authorised” and “captured” in the same way.
Demonstrate a successful collection followed by a delayed order update. Staff should check the source payment record before requesting another payment. Ask how a repeated event is recognised so the same collection does not post twice. Keep an exception queue with safe order and payment references, amount, status and owner. A missing confirmation email should trigger investigation, not an automatic second charge.
Agree a cross-channel returns procedure
Decide whether the store accepts online purchases at the counter and which system initiates the refund. Staff should locate the original order and payment rather than create an unrelated cash payout to simplify the interaction. Confirm how the refund reaches the website, processor, inventory and customer notification. A connector may support sales synchronisation without supporting every return scenario.
Test a partial return, a damaged item and an exchange for a different amount. A refund does not always mean the returned product is available for resale. Have the business approve stock disposition and staff permissions. Keep the original and correction references, and explain only the refund status the system has confirmed rather than promising an unsupported bank posting deadline.
Verify gift cards and promotions across channels
A gift card issued online may belong to a different programme from the store’s existing cards. Confirm where balances are stored and where redemption is permitted before promising that customers can use them anywhere. Test partial redemption, mixed tender and a return involving a gift balance. Identify how outstanding cards will be honoured after any system migration.
Promotions need clear eligibility, dates and interaction rules. Test an online-only discount at the counter and a counter-only offer online to ensure the expected restriction holds. Loyalty membership and promotional messaging should have their own approved customer flows. A previous purchase or loyalty enrolment should not be treated as blanket permission to add the customer to unrelated text campaigns.
Reconcile orders, collections and settlement
Compare the online order ledger with payment transactions using the same period and scope. Separate cancelled orders, refunds, shipping charges and other relevant entries. Match references before relying on grand totals. Then compare processor settlement with bank deposits using the actual settlement detail and account arrangement.
For an illustrative example, $900 of identified collections less $100 of recorded refunds produces $800 before other documented settlement entries. That is not automatically the bank amount. Fees, timing and other actual adjustments must be supported by records. Keep an exception list for approved payments missing from orders, duplicate posting and unexplained settlement differences, with a person responsible for each next step.
Give staff controlled access and a safe support routine
Separate catalogue editing, fulfilment, refunds and payment administration according to the business’s operating needs. Use individual accounts where supported and review access when staff change roles or leave. Keep payment credentials and unnecessary customer details out of ordinary email, website contact forms and shared job notes.
Record support ownership for the website, connector, payment service, hardware and settlement. When contacting Process Rite support, describe the affected stage, safe reference, time, expected result and actual result. Arrange document sharing after contact if needed. Confirm human availability and escalation arrangements directly rather than inferring continuously staffed support from an online enquiry form.
Compare complete costs and cancellation obligations
Use a realistic order count, sales volume, average ticket and refund pattern for every proposal. Add platform subscriptions, payment charges, required apps, connector fees, implementation, maintenance and equipment where relevant. Include charges from each organisation involved. Comparing only a processing headline can hide the cost of running the actual store connection.
Confirm term, renewal, cancellation, historical access, data export and responsibility for outstanding refunds. Hardware and software are separately quoted unless the written proposal expressly includes them. The pricing guide helps organise a complete comparison. A free statement review can identify questions and current charges; it does not guarantee savings, integration or approval.
Prepare for a connector interruption
Document how staff recognise stale stock or missing orders, who may pause online sales and how the business confirms the pause reached customers. Keep a way to identify orders received during the interruption without exposing customer details in an uncontrolled shared file. When service returns, reconcile the source orders and payments before replaying events or creating replacement orders.
Test a small recovery set: one paid order, one cancelled order and one stock update from the affected period. Confirm that each appears once, with the correct quantity and status. Resume normal operations only after the responsible employee has checked the backlog and assigned any remaining exceptions. A successful login to the connector is not proof that its queued work has completed.
Launch with a repeatable acceptance checklist
Test a standard shipped order, a pickup, a variant, the last stock unit, a failed payment and a partial cross-channel return. Write the expected customer message, inventory change, payment record and settlement reference before testing. Have a second employee repeat the workflow. Record any remaining manual steps and identify who performs them.
Preserve open orders, gift balances and required historical records before replacing the existing connection. Check old links from social profiles and automated emails, not just the homepage button. Review the first live orders, first settlement and first full statement after launch. The retail POS guide covers counter operations; the ecommerce decision should connect those operations to fulfilment without creating duplicate records.
Discuss your actual setup
Tell Process Rite your business type, current software, payment channels and the problem you want resolved. We arrange document sharing after contact. Do not include card details, bank credentials or customer records in the enquiry.
Request a free payments review · Understand the complete cost · Find the right support route
Hardware, software, apps and implementation are separately quoted. Availability, integration, pricing and approval require confirmation in the written proposal. A review does not guarantee savings or approval.