Lastaaminen

Channel Submissions

A Channel Submission records one external exchange or file-preparation operation for an External Listing. It ties the action to the exact approved content, configuration and destination identity, and preserves attempts, acknowledgment and issues.

The existing Data Export operation runs the queued work. The Channel Submission explains the channel-specific result; it is not a second scheduler.

For example, preparing an XML file can succeed while sending the same content to a merchant account remains unavailable. A later API submission can be accepted as input while provider processing reports a field rejection or restricted destination eligibility.

Actions and outcomes

Supported actions include file preparation, submission or update, withdrawal and reconciliation. The Connector's capabilities determine what can be performed.

Outcome What it establishes
File prepared The requested local artifact was generated
Submitted input The destination acknowledged an input exchange
Processed result The destination returned its processing result
Eligibility result The destination reported where the item may appear
Uncertain outcome Actualog cannot yet confirm the remote result

None of these facts alone establishes that a buyer can complete a purchase on the seller's website. That website must remain consistent with the published offer.

Who submits and where to inspect feedback

Catalog Managers and Company Administrators with channel-publication authority queue supported actions from the relevant listing. The executing worker rechecks current authority, connection validity and approved sources.

  1. Open the publication's External listings list.
  2. Preview and approve current content when required.
  3. Choose the intended submission, Prepare XML file, Withdraw external input or Reconcile external outcome action.
  4. Open Submissions and feedback, search the record and select View.
  5. Inspect the operation state, error code, corrective message, acknowledgment and attempt history.

The operation link provides the associated Data Export context. Keep the generated artifact's completion separate from the submission's external state.

Failures, retries and maintenance

Field validation failures require correction and reviewed content. Transient provider errors can be retried within the operation rules. Successful targets should not be republished merely because another target failed.

If a response is lost, unreadable or timed out, reconcile the stored destination identity before blindly replaying the operation. An uncertain result is not proof that nothing happened remotely.

Revoked credentials, lost permission, a paused publication or changed source information can stop queued execution. Review and approve a successor content version when the source changed. Preserve genuine acknowledgments and never replace provider feedback with assumed acceptance.

Related topics: External Listings, Company Integration Profiles, Publishing Catalog Offers.