Credentials never reach the browser
Marketplace credentials and provider keys stay server-side and are encrypted before persistence. The client bundle never contains them.
The publishing desk for local resale. Draft once, post to Craigslist and Facebook Marketplace through your own connected sessions, and every job ends in a named state instead of a spinner.
Nothing publishes on its own. Every job starts from a listing you send or a schedule you set. These defaults ride along on each Craigslist post and can be overridden per listing.
A channel reads live only after it has published in production. Partial support is named as partial. You will never meet a limit for the first time after signing up.
Session recall · form automation
Connect once · post for weeks
Not enabled in production
Assisted handoff under evaluation
completedfailed_preflightauth_requiredverification_requiredYour decisions, the marketplace's prerequisites and the job's result stay in separate columns. That separation is precisely why a failure here is recoverable instead of mysterious.
Photos, condition, location, category. Optional AI writes the title, description and a price with comparable sales attached.
Draft stays yoursA live browser window opens. You handle the password, the 2FA and any checkpoint. We keep the session, never the credential.
Session, not passwordEach destination becomes an independent signed job with its own retry policy, its own result and its own live URL.
Now or scheduledEvery job finishes in one of a small set of named states, so a failure tells you which prerequisite was missing rather than that something went wrong.
Never "something went wrong"Public status responses are deliberately limited, sensitive account actions require verification, and worker calls fail closed when a signing key or required configuration is missing.
Review security practicesMarketplace credentials and provider keys stay server-side and are encrypted before persistence. The client bundle never contains them.
Automation and message-ingestion requests require timestamped HMAC signatures, and stale payloads are rejected rather than replayed.
Email verification, password reset, MFA, data export and account deletion are all available in-product. Passkey enrolment stays off until login supports WebAuthn.
Neither Craigslist nor Facebook permits programmatic removal. Archiving pauses the listing here and opens the marketplace's own removal page. We do not claim a deletion we cannot perform.
Limits are read from the same entitlement source the application enforces at runtime. Nothing is hidden behind a tier that is not printed here.
Craigslist and Facebook Marketplace support connected publishing and scheduling. Lead Center is beta for buyer leads — incomplete by design, read-only (no send from SoukSync); keep checking each marketplace. Marketplace scrape sync stays off unless an operator enables it. eBay and OfferUp remain planned until production automation ships.
No. Listings begin as drafts. You choose the target marketplace and the publish time, and each selected destination reports its own job result.
The publish attempt is blocked before anything is sent, the prerequisite failure is recorded by name, and you are asked to refresh that connection before retrying. Nothing is posted half-way.
No. Authorisation happens in a live browser window that you drive. What persists afterwards is the session, not the credential, which is also why a session eventually needs renewing.
Yes. Account settings include a data export and a self-service deletion flow, and billing is managed through the Stripe customer portal.
Create an account, verify your email, and connect a supported marketplace when you are ready to publish. The free tier carries 3 active listings and 1 connection.