Current answers about using VizionLyst

VizionLyst is browser-based trading-card listing software that turns clear front-and-back card photos into reviewable eBay listing drafts. It assists with card identification, listing details, pricing context, and marketplace submission while keeping the seller responsible for checking the card, approving the final values, and choosing whether and when to publish.

VizionLyst is designed for trading-card sellers who want a repeatable path from card photos to reviewed eBay listings. It can support an occasional seller, a collector moving duplicates, or a higher-volume operation, but every user still needs to verify the physical card, commercial terms, account readiness, and marketplace result.

Get 20 free sets for 14 days. No card required. The trial begins when a verified account is provisioned and ends when 14 days pass or all 20 sets are used, whichever happens first. No monthly refresh. Unused sets do not carry into a paid plan.

One public trial per normalized email/account and connected eBay seller identity. A previous public trial tied to either identity blocks another trial for life. VizionLyst does not reveal another account's history when explaining ineligibility; an ineligible customer can compare paid plans instead.

VizionLyst currently provides separate Draft workflows for sports cards, Pokémon, Magic: The Gathering, and One Piece. Each Draft job uses one selected family, so mixed collections should be separated into multiple jobs. Support means the workflow is available; it does not guarantee every set, language, parallel, treatment, grade, or image will be identified completely.

No desktop installation is required for the supported product. VizionLyst runs in a web browser, where you sign in and use Settings, Draft, List, and History. A compatible browser, an active account, and internet access are still required because account state, uploaded images, processing jobs, billing, and eBay operations are handled by connected services.

No. VizionLyst provides reviewable assistance, not a guarantee of identification accuracy, appraisal value, listing acceptance, sale timing, or sale price. Image quality, available reference data, market conditions, seller settings, eBay requirements, and provider availability can all affect the result, so the seller must review and approve every listing decision.

You need an active VizionLyst account, access to the verified sign-in email for that account, the eBay seller account you intend to connect, and clear front-and-back photos of supported cards. Start with a small, single-family batch so you can confirm account readiness, photo pairing, draft review, pricing, and publishing controls before processing more inventory.

Use a verified email and create a password. VizionLyst's configured identity provider handles verification and credentials. Trial signup does not request a personal name or payment card. After provisioning, connect the eBay seller account you intend to use; that authenticated seller identity must be eligible before trial scans can begin.

Open the VizionLyst application and use the email tied to your active account. The configured identity provider handles sign-in, sign-up, recovery, and multi-factor authentication when available. If the identity does not map to an active VizionLyst account or the session cannot be verified, the application shows an account or session-required state instead of exposing workspace data.

VizionLyst uses an eBay connection to check seller readiness and submit only the listings you approve through the intended seller account. Authorization happens through eBay OAuth in the browser. The connection does not guarantee that eBay will accept a listing, and VizionLyst should never ask you to enter your eBay password inside the VizionLyst application.

Review Connection, Policies, Store Categories, Listing Text, and Automation before starting Draft work. The application guides incomplete accounts through the applicable readiness steps and provides a final path to Draft. A policy or store-category step should be skipped only when Settings offers that choice and the option truly does not apply to the connected seller setup.

1. Connect and confirm the intended eBay seller account.
2. Import and review the applicable policies and store categories.
3. Review reusable listing text and automation choices.
4. Use Go to Draft after the required readiness steps are complete.

Yes, when the connected account and eBay capabilities make them available. Settings can import supported shipping and return policies, store categories, and applicable mappings for seller review. Importing a value does not prove that every listing is ready; confirm the selected defaults, seller location, category requirements, and other eBay-owned fields before publishing.

VizionLyst currently accepts JPG/JPEG, PNG, HEIC, and HEIF card images. Use clear, readable, well-lit files that show the identifying text and available condition evidence. The service validates the declared file type and the image contents during upload, so renaming an unsupported or invalid file does not make it acceptable.

Provide one front image and one back image for each card, then review the proposed pair before processing. Draft uses selection and natural filename order as an organizational starting point, but you can swap image roles, move images between groups, or remove incomplete and mismatched groups. Consistent filenames make the initial pairing easier to inspect.

1. Select one card family for the batch.
2. Add one readable front image and one readable back image per card.
3. Confirm the image roles and pair membership before Start Review.

VizionLyst currently prepares a listing from two card images: one reviewed front image and one reviewed back image. Those images remain tied to the listing draft and are sent through the publishing workflow when available. If the listing needs additional photos, add them directly in eBay after the initial submission.

Draft is the image-intake and processing workspace. You select one supported card family, upload images, review the front-and-back pair groups, and start an account-scoped processing job. As work completes, VizionLyst records job progress and creates listing drafts for review in List; History retains durable job and result details.

A pair group is the two-image set assigned to one card before processing: one front and one back. Every active group must contain exactly two ready images before Start Review becomes available. Automatic grouping is not proof that the images belong together, so compare the proposed pair with the physical card and correct it first.

Start Review queues a durable Draft job for the valid pairs and selected card family. The backend retrieves the account-scoped uploads, attempts card identification and listing preparation, records item-level progress, and creates reviewable listing records when possible. Jobs may wait or run for different lengths of time depending on batch size, providers, and worker availability.

Yes. Draft jobs and their progress are account-scoped and durable, so refreshing the page or returning later does not intentionally create a replacement job. Use Draft for the active workflow and History for completed, failed, or canceled details. A queued state can be normal; inspect the displayed status before deciding to retry.

Not necessarily. Canceling can stop remaining work when the backend can honor the request, but it does not guarantee that attempted sets will be restored. VizionLyst checks available quota and records usage against the account before provider processing begins for that pair. The attempted set may count even if identification later fails, the job is canceled after work starts, the draft needs correction, or the seller does not publish.

List is the final review and publishing workspace for active listing drafts. It brings together the image pair, title, price, identity and condition fields, applicable policy readiness, status, and provider results. The seller reviews and corrects the values, waits for required persistence or pricing work, and chooses which ready listings to submit.

Compare the physical card and both images with the proposed identity, title, price, quantity, condition or grading fields, item specifics, policies, seller location, and any supported Best Offer thresholds. Also confirm that edits are saved and no required pricing refresh or provider-readiness warning remains. Generated or imported values should never be published without seller review.

1. Confirm the card identity, image pair, title, and item specifics.
2. Approve the final price, quantity, condition or grade, and offer thresholds.
3. Resolve policy, seller-location, persistence, and pricing warnings.
4. Submit only the ready listings you intend to publish.

Yes. Supported title, price, quantity, identity, condition, grading, item-specific, and offer values can be edited in List. Changes autosave after a short delay, and the row reports saving, saved, or retry states. Wait for the latest edit to persist before publishing; a failed autosave must be retried instead of being treated as an approved value.

A saved title or pricing-relevant identity change can start a separate durable pricing refresh so the recommendation reflects the listing you now intend to publish. The row can remain editable while that refresh runs, but submission stays blocked for unresolved pricing work unless a valid explicit final price satisfies the requirement. A recommendation may remain unavailable.

VizionLyst can use the reviewed card identity, active fixed-price eBay market data, account settings, and available provider capabilities to prepare pricing context and listing text. Recommendations and generated copy can be incomplete, delayed, or unavailable. Settings owns reusable listing text, while the seller remains responsible for the final price, description, item details, and marketplace compliance.

VizionLyst submits only the ready listing or listings you choose through backend provider routes for the connected eBay seller account. A successful response records the published state and available external identifier or URL. A validation, permission, policy, account, or provider failure remains attached to the listing for correction and is not silently treated as published.

A set represents one front-and-back card pair submitted for processing toward a listing draft. VizionLyst checks available quota and records usage against the account before provider processing begins for that pair. The attempted set may count even if identification later fails, the job is canceled after work starts, the draft needs correction, or the seller does not publish.

Remaining Sets summarizes the processing balance available to the signed-in account. A public trial shows its one-time balance out of 20, its end date, and no monthly refresh. Paid accounts distinguish the current monthly base allowance from manual credits and eligible purchased top-up sets, including the next base refresh date when one applies.

Your account and existing work remain available at either limit. Choose a paid plan for more scans. Settings, History, existing drafts, List, and otherwise eligible publishing remain available, but actions that start new scans are blocked. Unused trial sets do not carry into the paid allowance.

VizionLyst offers monthly plans with different set allowances and the same available core workflow, plus custom Enterprise Seller terms for larger needs. Eligible paid accounts can purchase separate 25-set top-ups from Settings. Use the Pricing page as the current source for plan names, allowances, prices, promotion eligibility, and purchase conditions.

Open the signed-in VizionLyst Settings page and choose Manage Subscription when billing management is available. Stripe owns the subscription-change and cancellation interface, while VizionLyst updates local access and quota from billing events. Review the plan, effective date, renewal state, and any charge or adjustment shown by Stripe before confirming the change.

1. Open the Account area in signed-in Settings.
2. Choose Manage Subscription to continue to Stripe.
3. Review the effective date and financial adjustment before confirming.

Do not assume a plan change is prorated or refundable. Stripe's confirmation screen shows the effective date and any immediate charge, credit, or other adjustment available for the account before confirmation. Digital subscriptions and set purchases are generally non-refundable unless the displayed checkout terms, a separate written agreement, or applicable law requires a different result.

VizionLyst uses its configured identity provider for account sign-in, sign-up, email verification, recovery, and multi-factor authentication when available. The application then maps the verified identity to an active VizionLyst account before returning workspace data. Use the provider's recovery flow for authentication problems and contact VizionLyst if the verified identity is not linked correctly.

No. VizionLyst should direct you to eBay's browser-based OAuth authorization flow instead of collecting your eBay password inside VizionLyst. eBay controls the authentication and consent screen, and the resulting connection is used by backend provider routes. Stop and contact support if a VizionLyst screen unexpectedly requests your eBay password.

No. A successful connection authorizes the available account workflow, but each listing still depends on current permissions, seller status, policies, seller location, category and item requirements, eBay validation, and provider availability. Review Settings and the listing failure details when a submission is rejected; do not repeatedly retry without correcting the reported blocker.

VizionLyst processes account information, uploaded card images, listing inputs and outputs, billing events, provider connections, and support information to operate the service. Different service providers handle identity, payments, storage, email, AI assistance, and marketplace operations. Review the Privacy Policy for the current purposes, disclosures, retention considerations, choices, and contact path.

Confirm the file is a valid JPG/JPEG, PNG, HEIC, and HEIF image and that the card is readable. Retry the individual file or remove it from the batch; a failed upload must not remain in an active pair. Renaming an unsupported file is not enough because VizionLyst validates its type and decoded image contents.

Start Review remains unavailable until the batch has at least one valid pair and every active pair contains exactly two ready images. Wait for uploads to finish, retry or remove failed files, and correct incomplete or mismatched groups. Also confirm that another Draft job is not already active for the account before starting new work.

A queued job can continue without the page remaining open, so first check its current Draft or History status instead of starting a duplicate. If the job or an item fails, inspect the displayed stage and message, correct any actionable image, account, quota, or provider issue, and retry only when the blocker has been addressed.

Finish the title and identity corrections, wait for the latest pricing refresh, and review any pricing-specific error. A recommendation can remain blank when market data is unavailable or inconclusive. Enter a valid final price manually when appropriate, allow it to autosave, and confirm the row is ready before attempting to publish.

Read the listing's attached failure details and confirm the connected account, price, quantity, condition or grading values, policies, seller location, category, item specifics, and other required fields. Correct the reported problem and wait for edits to save before retrying. Provider outages or permission issues may require waiting or updating the eBay account first.

1. Read the exact failure category and safe provider message attached to the listing.
2. Correct the applicable listing value or account-readiness problem.
3. Wait for the correction to save, then retry only that intended listing.

Use the Contact page or email support@vizionlyst.com for product, access, billing, security, privacy, or workflow help. Include the affected screen, the safe error message, and what you were attempting, but do not send passwords, authentication codes, OAuth state, provider tokens, payment-card details, or other secrets in the request.