oneVegetable

oneVegetable oneVegetable is a local operations workspace for Alibaba.com international sellers. It brings products, image and video assets, inventory, RFQs, trade, logistics and audited Open Platform capabilities into one Manifest V3 extension. oneVegetable is an independently developed third-party tool and is not affiliated with, endorsed by, sponsored by, or officially associated with Alibaba.com or its affiliates. Before use, read and follow the Alibaba.com platform rules and any rules applicable to your business. New users should start with IOP; merchants with an existing legacy application can continue using TOP. Unmarked historical bundles and existing settings retain TOP compatibility. Save the two authorizations separately, remember a preferred default or route by verified capability. You must ensure they belong to the same merchant; the tool does not verify merchant identity. Configuring one never replaces the other, and uncertain writes are never retried through the other protocol. Full feature equivalence is not promised, unsupported operations stay blocked and real failures never show simulated responses. Key features (subject to the selected protocol and account permissions): Review authorization time remaining in Overview: yellow below half of the current lifetime and red below one quarter or after expiry. Unknown expiry is never guessed, and display changes never automatically renew a token. Visually edit Schema-based products and standard descriptions, choosing category-supported direct-order or inquiry/custom types when creating a product. Fill text-only placeholders and compose up to ten safe company, logistics or other templates in order, then preview before insertion, append or confirmed replacement. The standalone extension stores templates locally; backend sites share them. Saving a template never updates a product automatically. Exchange templates through JSON, image-inclusive ZIP or S3 previews. Relative image paths and integrity manifests replace original file IDs; confirm a target image group and verify uploads before saving new URLs. ZIPs are limited to 50 MiB, credentials stay out of packages and uncertain uploads are not automatically resent. Select up to 30 existing formal products, preview group and keyword differences, deselect individual items and confirm serial updates. Only changed fields are sent; account or credential changes stop the workflow. Accepted requests still await platform review and field readback. Batch receipts stay in the task center; unknown writes are never resent automatically, and no bulk group-clearing or automatic-rollback control is added. Search, show, hide and reorder optional columns in supported lists, with fixed selection/action columns and consistent search, filter and row-action controls. Filters apply only on confirmation; repeating the same search queries again. Read product/SKU inventory in a dedicated workspace or shared drawer, with current-page, selected-row and individual queries, progress and a stop control. Empty or unqueried records are not zero stock, quantities are not summed across sources, and inventory is never modified. Inspect showcase quota and products, then confirm additions, removals, reordering or replacement and verify by read-back. Uncertain writes are never automatically retried; removing a showcase entry does not delete the product. Import and export products as JSON or ZIP archives with managed assets image resources. Select gallery assets and receive non-blocking content guidance. Browse paginated images and videos under Assets with full-screen previews. Images support 24/48/96-item pages; video relations load on demand, and platform review and quality remain distinct. Confirm uploads of local MP4 files up to 50 MiB through multipart staging in your configured S3 storage, or supply a public HTTPS video URL. Real upload and readback passed for the formal extension and local Node backend; Worker real uploads remain disabled. Resume manually with the task and original file or same URL. Unknown writes are never automatically resent; acceptance is not confirmed readback, and completed S3 objects and platform videos are not automatically deleted. Select an existing product from a video list or a confirmed upload task, or select and preview videos in the product editor and verify relations with read-only requests. Real relation writes remain disabled; selecting a video or product never automatically changes a product. Import and export gallery ZIPs up to 50 MiB with originals and an integrity manifest; uploads require confirmation. Connect directly to S3-compatible storage and map prefixes to gallery groups without deploying a backend. Pause, verify and resume ZIP/S3 tasks from local transfer history. Transfers continue across dialogs and workbench navigation, but require manual confirmation after reload. Confirmed items are not resent and uncertain results are not presented as complete success. Share one gallery asset through the operating system, export a sharing package, or publish it through the user's own backend to a connected Facebook Page or Instagram professional account. Search RFQs and edit quotations in the current page in TOP mode; RFQ remains unsupported in IOP. New product/RFQ edits are not automatically persisted or restored; leaving a changed form requires confirmation. Legacy edit drafts are not read, restored, migrated or automatically deleted. Platform drafts, batch queues and durable tasks remain available. Combine order, logistics and fulfillment information within the selected protocol's supported scope. Order funding remains TOP-only; IOP never substitutes fees or fabricated data for paid amounts. Search audited and typed Open Platform capabilities, including 35 additional request/response contracts, examples and permission/prerequisite details. Integration does not grant account access; restricted APIs and disabled writes remain unavailable. Inventory, product, gallery and video checks explain delayed platform updates. An acknowledged request may still read back old values; uncertain results require verification, not automatic resubmission or a promised synchronization time. Follow a four-step visual journey through developer registration, platform review, application setup, and OAuth, with in-page guidance that does not read submitted registration details. Reuse the current Alibaba sign-in to obtain credentials from an existing application. Choose offline file import or online connection before selecting TOP/IOP. Import one JSON bundle or an array containing both protocols; the complete input must validate before import. Historical files without a protocol remain TOP. Use the independent TOP/IOP authorization, renewal and credentialInfo.json export tool without deploying a separate local service. IOP first reads an existing application. If the old TOP entry is unavailable, supply your original application details or your own backup; IOP keys are never substituted and legacy applications are not created automatically. Explicitly import and save the result in the workbench without replacing the other protocol. Unknown renewal outcomes are not automatically retried. Set an optional local protection passphrase, shared by Authorization and Settings, or leave it blank to use a random device key. Existing passphrase users retain their original protection; browser restarts and extension updates do not automatically lock it. Sync to-dos through Chrome sync storage, retaining pending local changes while offline. Older local to-dos sync only after explicit migration; credentials and keys never participate. Review product, batch, asset-transfer and video receipts in the unified task center, with account-scoped source and verification links. Viewing history never automatically resends, resumes or modifies products. Manage credentials, S3 storage, connections and language in separate settings sections. Switching sections preserves unsaved input; import rules expand on demand. Use the dedicated Logs page for redacted diagnostics, local data and optional host permissions. Backend administrators can also inspect request diagnostics and audit events. Unlock later after manual locking while keeping non-credential features available, and use Logs to inspect or clear local data, session diagnostics, guarded product-mutation and video-upload tasks, social-backend device authorization and optional host grants. The extension runs no advertising or analytics service. The credential assistant accesses only the known Alibaba Application Center and OAuth tabs after the user starts it, and it neither collects the website password nor bypasses human verification. Credentials are encrypted on the user's device using an optional passphrase of at least 6 characters, or a random device key when left blank; extension content scripts cannot access storage and the passphrase is not stored. Derived recovery keys persist in trusted chrome.storage.local, never in Chrome sync and never as plaintext tokens. Browser restarts, extension updates/reloads or disable/re-enable do not automatically lock it, and there is no idle auto-lock. In passphrase mode, manual workbench lock clears the workbench and independent TOP/IOP tools' recovery keys; a tool-local lock affects only its selected protocol. After manual lock, passphrase mode requires the original passphrase; device-only mode requires an explicit unlock click without an additional passphrase barrier. Old bundles require their original passphrase once to enable recovery; clearing authorization also clears its recovery material. Keeping key material beside ciphertext reduces offline protection: a full browser-profile copy may be decrypted without the passphrase. This is not an independent password safe. Requests are sent only after a user action: in TOP mode, guarded platform drafts, new-product publishing, product-content updates, product listing/unlisting, product-group creation, gallery group management, image upload, and external-image transfer are enabled after real-account validation. IOP enables only its three independently accepted Schema writes, subject to existing confirmation and mutation gates. Unverified Alibaba write operations are blocked before network access. Product-content and display changes record a minimal local task before sending, then read Schema or the product list back to verify the final state; listing/unlisting also supports explicit recovery to the original state. Official social publishing requires the user's own oneVegetable backend and Meta application. The extension requests access only to that exact backend when the user starts pairing and stores a revocable, scoped 30-day device token; it does not store a Meta App Secret or platform token. An image is sent through the user's backend to Meta only after the user selects one image, a destination and a caption and confirms again. Video uploads use a separate guarded task workflow, not generic debugger writes or product-video association. Tasks retain titles, filenames and fingerprints, multipart metadata and receipts, not file bytes, Base64, source or signed URLs, or credentials. Submission sends the video address to Alibaba for retrieval. Video staging reuses your authorized S3 host and adds no extension permission. The template library supports safe reusable company and logistics content, JSON/S3 exchange, archiving and restoration. Backend sites share templates; the standalone extension stores them locally. Inserting a template never updates an Alibaba product automatically. Batch maintenance reuses the enabled product-update API without additional permissions. Tasks retain only minimal receipts, batch/account context and target-field fingerprints, not full XML or unsubmitted editing rules. Platform acceptance, review approval and field readback are distinct results, with no promised synchronization time. Uncertain writes are never resent automatically and changes are not rolled back automatically. No bulk group-clearing control or new extension permission is added. These materials prepare a release; they do not establish Store publication or deployment.