Plugin identity changed to ServisPin (new folder\/file\/text-domain: servispin). If you're moving from an install named "Pincode Delivery Estimator", install this as a new plugin and deactivate\/remove the old one \u2014 WordPress treats them as separate plugins, though your existing pincode data, settings, and shortcodes carry over untouched since none of the internal identifiers changed.<\/p>"},"ratings":[],"assets_icons":{"icon-128x128.png":{"filename":"icon-128x128.png","revision":3672863,"resolution":"128x128","location":"assets","locale":"","width":128,"height":128},"icon-256x256.png":{"filename":"icon-256x256.png","revision":3672863,"resolution":"256x256","location":"assets","locale":"","width":256,"height":256}},"assets_banners":{"banner-772x250.png":{"filename":"banner-772x250.png","revision":3672863,"resolution":"772x250","location":"assets","locale":"","width":772,"height":250}},"assets_blueprints":{},"all_blocks":[],"tagged_versions":["1.7.7"],"block_files":[],"assets_screenshots":{"screenshot-1.png":{"filename":"screenshot-1.png","revision":3672883,"resolution":"1","location":"assets","locale":"","width":3418,"height":1648},"screenshot-2.png":{"filename":"screenshot-2.png","revision":3672883,"resolution":"2","location":"assets","locale":"","width":3418,"height":1648},"screenshot-3.png":{"filename":"screenshot-3.png","revision":3672883,"resolution":"3","location":"assets","locale":"","width":3418,"height":1648},"screenshot-4.png":{"filename":"screenshot-4.png","revision":3672883,"resolution":"4","location":"assets","locale":"","width":3418,"height":1648},"screenshot-5.png":{"filename":"screenshot-5.png","revision":3672883,"resolution":"5","location":"assets","locale":"","width":3418,"height":1650}},"screenshots":{"1":"Frontend pincode checker widget.","2":"Delivery result \u2014 estimated date, express and COD\/Prepaid badges.","3":"The \"Check Now\" popup.","4":"The persistent delivery bar.","5":"Admin \u2014 pincode management (list, search, filters, bulk actions).","6":"Admin \u2014 Bulk CSV upload, with the sample template download and import summary.","7":"Admin \u2014 Settings screen."}},"plugin_section":[],"plugin_tags":[13827,5142,66014,3546,286],"plugin_category":[45],"plugin_contributors":[278361],"plugin_business_model":[],"class_list":["post-353290","plugin","type-plugin","status-publish","hentry","plugin_tags-delivery","plugin_tags-estimator","plugin_tags-pincode","plugin_tags-shipping","plugin_tags-woocommerce","plugin_category-ecommerce","plugin_contributors-officialwebfoo","plugin_committers-officialwebfoo"],"banners":{"banner":"https:\/\/ps.w.org\/servispin\/assets\/banner-772x250.png?rev=3672863","banner_2x":false,"banner_rtl":false,"banner_2x_rtl":false},"icons":{"svg":false,"icon":"https:\/\/ps.w.org\/servispin\/assets\/icon-128x128.png?rev=3672863","icon_2x":"https:\/\/ps.w.org\/servispin\/assets\/icon-256x256.png?rev=3672863","generated":false},"screenshots":[{"src":"https:\/\/ps.w.org\/servispin\/assets\/screenshot-1.png?rev=3672883","caption":"Frontend pincode checker widget."},{"src":"https:\/\/ps.w.org\/servispin\/assets\/screenshot-2.png?rev=3672883","caption":"Delivery result \u2014 estimated date, express and COD\/Prepaid badges."},{"src":"https:\/\/ps.w.org\/servispin\/assets\/screenshot-3.png?rev=3672883","caption":"The \"Check Now\" popup."},{"src":"https:\/\/ps.w.org\/servispin\/assets\/screenshot-4.png?rev=3672883","caption":"The persistent delivery bar."},{"src":"https:\/\/ps.w.org\/servispin\/assets\/screenshot-5.png?rev=3672883","caption":"Admin \u2014 pincode management (list, search, filters, bulk actions)."}],"raw_content":"\n
ServisPin lets customers enter their pincode and instantly see an estimated delivery date for their location \u2014 without leaving the page.<\/p>\n\n
A shopper types a 6-digit pincode, the plugin looks it up over AJAX against a database you manage, and shows the delivery estimate (plus an optional expected date, express-delivery badge, and COD\/Prepaid availability) right where they're shopping. It's built for WooCommerce, with AJAX lookup, admin pincode management, CSV bulk import\/export, shortcodes, and a persistent delivery bar that remembers a customer's pincode as they browse.<\/p>\n\n
WooCommerce is optional.<\/strong> The shortcodes, admin panel, AJAX lookup, delivery bar, and CSV tools all work on any WordPress site with no WooCommerce dependency. WooCommerce is only used for one specific feature \u2014 an optional compact checker that can appear directly on single product pages \u2014 which simply doesn't appear if WooCommerce isn't installed, with no errors or broken functionality either way.<\/p>\n\n ServisPin does not send your customers' pincode lookups, delivery data, or any store data to any external server. All pincode lookups are handled entirely by your own WordPress site's database and AJAX endpoint \u2014 nothing about what a customer searches for leaves your site.<\/p>\n\n Rate limiting.<\/strong> To reduce scripted abuse of the public pincode-lookup endpoint, the plugin temporarily hashes (MD5) the visitor's IP address and uses that hash as a counter key in a short-lived WordPress transient (auto-expires after 60 seconds). The raw IP address itself is never stored, never logged, and never transmitted anywhere \u2014 only the hash-based counter exists, and only for one minute.<\/p>\n\n Uninstall feedback (fully optional).<\/strong> When an administrator deletes ServisPin from the Plugins screen, an optional feedback popup appears. Nothing is sent unless the administrator explicitly clicks \"Submit Feedback\" \u2014 clicking \"Skip & Uninstall\" (or simply not submitting) sends nothing at all. If feedback is submitted, it is emailed via WordPress's native Local storage.<\/strong> To remember a customer's last-checked pincode between page loads, the frontend widget stores that pincode and its delivery result in the visitor's own browser (via ServisPin does not load any external service, font, API, analytics, or tracking script anywhere in the plugin. All CSS, JavaScript, and fonts are bundled locally and served from your own site \u2014 nothing is fetched from Google, a CDN, or any other third-party domain. (Earlier versions loaded the \"Poppins\" font from Google Fonts for the frontend widget; this has been replaced with the operating system's own font, so no such request is made anymore.)<\/p>\n\n\n WooCommerce is not required \u2014 the shortcodes, admin panel, AJAX lookup, and delivery bar all work on any WordPress site without it. When WooCommerce is active, ServisPin can additionally show a compact delivery checker directly on single product pages (via the Yes, via ServisPin \u2192 Bulk Upload<\/strong>. Upload a CSV with Yes. The Bulk Upload screen has a \"Download Sample CSV Template\" button that generates a CSV using the exact column headers the importer expects, with a few example rows, so you can fill it in and re-upload it directly.<\/p><\/dd>\n Yes, from ServisPin \u2192 Import\/Export<\/strong>, as a CSV containing all your pincode records.<\/p><\/dd>\n Yes. The customer-facing checker (in the shortcode widget, the \"Check Now\" popup, and the product-page checker) looks up a pincode over AJAX and shows the result without reloading the page. The pincode is validated and sanitized server-side regardless of what the browser sends.<\/p><\/dd>\n Yes. Once a customer has checked a pincode, a \"Change\" link (in the message shortcode and the persistent delivery bar) reopens the same popup so they can look up a different one. The last checked pincode is also remembered (via the browser's local storage) and automatically re-verified on the next page load.<\/p><\/dd>\n Yes, two: Yes. Both shortcodes render through WordPress's standard shortcode mechanism, so they work inside Elementor's Shortcode widget the same way any other shortcode does.<\/p><\/dd>\n Yes, via the core Shortcode block, for the same reason \u2014 no special integration is required.<\/p><\/dd>\n No, not unless you explicitly opt in. Under ServisPin \u2192 Settings<\/strong>, \"Delete Data on Uninstall\" is OFF by default \u2014 your pincode table and settings are preserved unless you turn that on before deleting the plugin. When you do delete the plugin from the Plugins screen, you'll also see an optional, skippable feedback prompt \u2014 it never blocks deletion and is never sent unless you choose to submit it.<\/p><\/dd>\n The lookup endpoint is intentionally public (customers aren't logged in when checking delivery). It validates and sanitizes the pincode server-side, verifies a nonce, and applies a lightweight per-IP rate limit to reduce scripted abuse without affecting normal shoppers.<\/p><\/dd>\n\n<\/dl>\n\n\nFeatures<\/h3>\n\n
\n
[pincode_delivery_estimator]<\/code> (the full checker widget, also available in a compact style) and [pincode_delivery_message]<\/code> (a small \"Check your delivery date\" prompt, or the customer's last result once they've checked).<\/li>\n.pde-<\/code> prefix throughout) so the plugin's styles don't clash with your theme or other plugins.<\/li>\nPrivacy<\/h3>\n\n
wp_mail()<\/code> to the developer (webfoo.in@gmail.com) and contains only: the selected reason, the typed feedback text, the plugin version, the WordPress version, the PHP version, and the date\/time. It never includes the site's URL, the administrator's identity or email address, IP addresses, cookies, or any authentication data.<\/p>\n\nlocalStorage<\/code>). This data stays on the visitor's device \u2014 it is not a cookie, and it is not sent to or stored on the server beyond the normal AJAX lookup that produced it.<\/p>\n\nExternal Services<\/h3>\n\n
\n
[pincode_delivery_estimator]<\/code> shortcode to any page, post, or shortcode-compatible page builder block where you want the checker to appear \u2014 or use [pincode_delivery_message]<\/code> for a smaller \"Check your delivery date\" prompt.<\/li>\n\n
Does ServisPin work with WooCommerce?<\/h3><\/dt>\n
woocommerce_single_product_summary<\/code> hook), toggleable from Settings.<\/p><\/dd>\nCan I import pincode data in bulk?<\/h3><\/dt>\n
pincode<\/code> and delivery_days<\/code> columns (optionally city<\/code>, state<\/code>, express_available<\/code>); existing pincodes are updated, new ones are added, and you get an import summary (total, added, updated, invalid\/skipped rows).<\/p><\/dd>\nCan I download a sample CSV?<\/h3><\/dt>\n
Can I export pincode data?<\/h3><\/dt>\n
Does ServisPin support AJAX lookup?<\/h3><\/dt>\n
Can customers change their pincode?<\/h3><\/dt>\n
Does ServisPin support shortcodes?<\/h3><\/dt>\n
[pincode_delivery_estimator]<\/code> (the full checker widget; add style=\"compact\"<\/code> for a smaller version) and [pincode_delivery_message]<\/code> (a compact \"Check your delivery date\" prompt\/result).<\/p><\/dd>\nCan I use ServisPin with Elementor?<\/h3><\/dt>\n
Can I use ServisPin with Gutenberg?<\/h3><\/dt>\n
Does uninstalling ServisPin delete my data?<\/h3><\/dt>\n
Is the public pincode-lookup endpoint safe from abuse?<\/h3><\/dt>\n
1.7.7<\/h4>\n\n
\n
1.7.6<\/h4>\n\n
\n
1.7.5<\/h4>\n\n
\n
\/* translators: *\/<\/code> comments for %d<\/code> placeholders in the CSV import summary and export panel.<\/li>\n1.7.4<\/h4>\n\n
\n
1.7.3<\/h4>\n\n
\n
[servispin_delivery_estimator]<\/code> \/ [servispin_delivery_message]<\/code> shortcodes as the primary ones, with a note that the older [pincode_delivery_estimator]<\/code> \/ [pincode_delivery_message]<\/code> names still work for existing content.<\/li>\n<\/ul>\n\n1.7.2<\/h4>\n\n
\n
1.7.1<\/h4>\n\n
\n
pde_save_settings<\/code> \/ pde_save_pincode<\/code> \/ pde_bulk_upload<\/code>, but the save handler was checking for the new servispin_*<\/code> names. This meant nothing typed on those three forms was ever saved \u2014 no error was shown, it just silently didn't take effect. Deleting and toggling status (which use link-based actions, not these forms) were unaffected. All three buttons now match the handler and save correctly.<\/li>\nload_plugin_textdomain()<\/code> call. WordPress.org-hosted plugins have had their translations auto-loaded since WP 4.6, so the call was redundant (per WordPress.org Plugin Check).<\/li>\npde_duplicate<\/code>, pde_db_error<\/code>) to servispin_duplicate<\/code> \/ servispin_db_error<\/code> for full identifier-prefix consistency.<\/li>\n<\/ul>\n\n1.7.0<\/h4>\n\n
\n
PDE<\/code>\/pde<\/code> to the unique ServisPin<\/code>\/servispin<\/code> (classes, constants, the global bootstrap function, AJAX actions, hooks, nonces, the settings group, and script\/style handles). This addresses WordPress.org Plugin Check's \"prefix too short\" requirement.<\/li>\n[servispin_delivery_estimator]<\/code> and [servispin_delivery_message]<\/code>. The original [pincode_delivery_estimator]<\/code> and [pincode_delivery_message]<\/code> continue to work unchanged for existing content.<\/li>\n1.6.3<\/h4>\n\n
\n
1.6.2<\/h4>\n\n
\n
1.6.1<\/h4>\n\n
\n
1.6.0<\/h4>\n\n
\n
1.5.0<\/h4>\n\n
\n
1.4.0<\/h4>\n\n
\n
pincode-delivery-estimator<\/code> to servispin<\/code> to match the final public plugin identity. Internal identifiers that existing installs rely on \u2014 the database table, option names, AJAX actions, shortcodes ([pincode_delivery_estimator]<\/code>, [pincode_delivery_message]<\/code>), and CSS classes \u2014 are all unchanged, so existing pincode data and shortcode usage in your content continue working without edits.<\/li>\nreadme.txt<\/code> Contributors to the confirmed WordPress.org account (officialwebfoo<\/code>).<\/li>\n== Privacy ==<\/code> and == External Services ==<\/code> sections documenting the plugin's rate-limiting IP hashing, the optional uninstall-feedback email, local-storage usage, and the Google Fonts request \u2014 accurately reflecting the existing implementation, with no new data collection introduced.<\/li>\n1.3.2<\/h4>\n\n
\n
id=\"delete-{slug}\"<\/code> pattern), in case a site's markup doesn't match the first two detection strategies.<\/li>\n<\/ul>\n\n1.3.1<\/h4>\n\n
\n
1.3.0<\/h4>\n\n
\n
wp_mail()<\/code>; skipping it \u2014 or any failure to send \u2014 never blocks or delays uninstalling, and the existing opt-in data-deletion behavior in uninstall.php<\/code> is unchanged.<\/li>\n1.2.1<\/h4>\n\n
\n
PDE_Database::update()<\/code> on partial updates (e.g. activate\/deactivate), which only ever send a status<\/code> field.<\/li>\n=<\/code>, +<\/code>, -<\/code>, or @<\/code> to prevent spreadsheet formula injection when opened in Excel\/Sheets. Normal values (city, state, pincode, delivery estimate) are unaffected.<\/li>\nflush_rewrite_rules()<\/code> call on deactivation (the plugin registers no rewrite rules, post types, or taxonomies).<\/li>\n1.2.0<\/h4>\n\n
\n
[pincode_delivery_message]<\/code> no longer renders blank before a search \u2014 it now shows a \"Check your delivery date\" prompt with a \"Check Now\" link.<\/li>\n1.1.1<\/h4>\n\n
\n
1.1.0<\/h4>\n\n
\n
express_available<\/code> column).<\/li>\nexpress_available<\/code> database column (auto-added on upgrade via dbDelta \u2014 no manual migration needed).<\/li>\nexpress_available<\/code>.<\/li>\n<\/ul>\n\n1.0.1<\/h4>\n\n
\n
1.0.0<\/h4>\n\n
\n